Manual Planning

Use this skill to produce Markdown plans that another coding agent can execute without reinterpreting the original conversation. Keep plans stable, explicit, and easy to update mechanically.

Default Location

Create the plan in docs/ when that directory exists. Otherwise create it at the repository root.

Use a descriptive kebab-case filename such as docs/payment-refactor-plan.md or manual-plan.md. Avoid temporary names like notes.md, scratch.md, or todo.md.

Plan Creation Workflow

1. Gather enough repository context to identify scope, dependencies, test surfaces, and likely risks.
2. Draft the plan as a Markdown file using one of:
   • assets/simple-plan-template.md for 10 or fewer tasks.
   • assets/milestoned-plan-template.md for more than 10 tasks.
3. Set Plan Status to QUESTIONS PENDING if clarification is required, then surface all clarifying questions to the user. Put the same unresolved questions in the plan under Open Questions.
4. Incorporate the answers, then self-check the whole plan before requesting final approval.
5. Set Plan Status to READY FOR APPROVAL only when the self-check passes and the only remaining gate is user approval.