Postmortem

Turn a finished (or stuck) piece of work into a short, honest postmortem that ends in concrete fixes — not vibes. The output is for next time: cheaper round-trips, fewer user corrections, a skill/config/code edit that bakes the lesson in.

The one rule

One well-briefed reviewer, not a panel. It is tempting to run several agents in different "formats" (5-Whys, timeline, start/stop/continue) for thoroughness. Don't — they converge on the same findings and you pay N× the tokens for one diagnosis. A single agent, given the full facts and asked for all three artifacts in one pass, produces the same conclusions. (Spend the budget on the brief, not on copies of the agent.)