Skip to lesson
Exit
Review, Edit and Save Plans1 / 2

2 min lesson

Stop when you have proof

Connect "Start with this check: Every step has an owner: Agent, human or external system" to the decision you would make.

Step 1 of 2

The job: the plan can be reviewed, edited, saved and used as the implementation contract. Start with this check: Every step has an owner: Agent, human or external system. Keep it small enough to check the result yourself instead of taking the summary on trust.

Prune the plan, add a gate, then keep it as the contract

0:43 · narrated
Read this demo as text
  1. Plan Mode writes this out as prose, not a checklist with an approve button. It's Markdown, sitting right there — you can edit it directly, and nothing builds until you say go.
  2. Step 3 stands up a brand-new Redis client, but billing already owns one — that doesn't serve this task, so delete it right in the plan text. Add an out-of-scope line and a verify gate while you're editing.
  3. Now every step has an owner — Agent, the reviewer, or CI — and the verify gate lives in the plan itself. That's the version the build and the review both point to.
Prune the plan's own Markdown, add a verify gate and owners, then treat the revised plan as the contract.

Practice next: Now try it: open a plan the agent wrote, cut what doesn't serve the task, add a verify gate, and tag each step with its owner.

Simulated Cursor 3.12 (macOS, light) — beta educational reconstruction, not the real product.