writing-plans

name	writing-plans
description	Use when: write a structured implementation plan before starting a complex or multi-step task.

Goal: produce a plan an agent can execute step by step with verification.

Use for:

• multi-file changes, migrations, or features with ordering risk
• work that will be handed to another session or subagent
• tasks where mistakes are expensive to unwind

Workflow:

1. State the outcome and how success is verified.
2. Map current state: files, interfaces, and constraints involved.
3. Break work into ordered tasks with explicit dependencies.
4. For each task define the change and its verification step.
5. Mark checkpoints where progress is committed.
6. List risks, blockers, and what to do when verification fails.

Plan shape:

• goal and acceptance criteria
• ordered tasks with per-task verification
• checkpoints and rollback points
• risks and open questions

Rules:

• every task must be independently verifiable
• prefer small reversible steps over large rewrites
• do not bury assumptions inside steps; list them up front
• keep the plan in the repo so execution can reference it