kimtth 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:
- State the outcome and how success is verified.
- Map current state: files, interfaces, and constraints involved.
- Break work into ordered tasks with explicit dependencies.
- For each task define the change and its verification step.
- Mark checkpoints where progress is committed.
- 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