Run the produce–critique–revise pattern
Everyone · Direct the work
Steps at a glance
1. Choose the deliverable and the quality bar
This pattern suits anything where a first draft is cheap and quality comes from challenge: a how-to guide, a background article, a project plan, a stakeholder-facing summary.
Say up front what good looks like. Critics with no standard produce style notes.
2. Assign a producer
One agent drafts. Give it the source material and the format — for a how-to guide, that means the analysis it should draw on and the template it should fill.
3. Assign critics on different models
Two critics, deliberately on different models. This is the point of the pattern: models share blind spots with themselves and not with each other, so two critics on the same model largely duplicate one critic.
Give each critic a distinct lens rather than "review this" — for instructional content, one on soundness (is this accurate, complete and correctly structured) and one on the reader's experience (could someone actually follow this at the moment they need it).
4. Send it back for revision
The producer revises against the critique. Ask it to say what it changed and what it rejected — an agent that silently drops a critique it disagreed with has hidden a decision from you.
5. Review as the human and decide
You are not the fourth reviewer; you are the one who decides. The output of this pattern is a better draft, not an approved deliverable.
For anything your team requires human sign-off on, this pattern gets you to a candidate — the sign-off is still yours, and for the highest-stakes content the writing itself may still belong to a human. See Run a project with agent oversight levels.
Verified against Buzz v0.5.20 · Updated 2 Sep 2026