2 min lesson
Plan review and saved plan workflow
Complete "Plan review and saved plan workflow". Check the final state against the lesson before you move on.
Check your understanding
Run this practice: Plan Mode — prune the plan, add a gate, then save it as the contract.
Outcome: The saved plan lists every step with an owner beside it — Agent writes the limiter, the reviewer approves the threshold, CI runs the gate — so whoever picks it up next knows exactly who runs what.
Plan Mode — prune the plan, add a gate, then save it as the contract
Plan review and saved plan workflow
SayThe Plan Mode output reads like a mini design doc. Step 3 stands up a new Redis client, but billing already owns one, so that step doesn't serve the task.
DoDelete step 3 in the plan's Markdown — you revise the Markdown directly, and nothing is built until you approve it.
Type
## Out of scope: metrics dashboard
## Verify: `pnpm test rate-limit` and `pnpm lint` pass before mergeSeeThe verification gate and the out-of-scope line now sit in the plan, so a future reader sees the boundary and the proof step, not just the happy path.
SayTag each step with its owner, and reference the token-bucket method rather than our lib path, so a teammate could run this in a different repo.
DoAdd an owner to every step — Agent, the reviewer, or CI — keeping the language method-first instead of file-first.
DoSave the plan so it guides the follow-up work and the team review.
SeeThe saved plan lists every step with an owner beside it — Agent writes the limiter, the reviewer approves the threshold, CI runs the gate — so whoever picks it up next knows exactly who runs what.
Learn more
Optional practice
Practice: Plan review and saved plan workflow
QYou've applied it. What actually proves the work is done, not just a plausible answer?