Up to now you learned individual techniques: insist with specific questions, correct surgically, reaffirm, restart. This lesson brings them together as 5 patterns that you'll apply combined in production.
These aren't the only patterns. they're the most practical to start with. Once you have them in your head, you can combine them as the situation needs.
| Pattern | When |
|---|---|
| Drafter-Reviewer | Output that needs rigor. any deliverable going to a final user. |
| Expert-asks-back | Start of a task where the model needs inputs it doesn't have. |
| Devil's advocate | Important decisions before executing. |
| Recap-then-ask | Long conversation at a decision point. |
| Ping-pong refine | Polish an output close to the end, without losing what's good. |
On the right you have the 5 patterns side by side. Before closing the track, internalize them as separate tools: each one solves a different problem. If you use them all for everything, that's overengineering. If you use them per case, you're an expert multi-turn operator.
These same patterns replicate in human work. Drafter-reviewer is what a PM does before sending a doc to the team. Expert-asks-back is what a consultant does in the first meeting. Devil's advocate is what separates a good decision from a quickly-made one.