Write Plan
Overview
Produce a complete, self-contained implementation plan that can be executed by
execute-plan
with minimal ambiguity.
This skill is for planning only:
Do not implement code
Do not modify production files (except plan artifacts)
Artifact Conventions
Use one consistent artifact structure for every plan:
Plan directory:
docs/plans/YYMMDD-HHmm-
Implementation Plan:
Created: YYYY-MM-DD HH:mm:ss
Status: Draft
Objective
What is being built/changed and why.
Scope
In scope
Out of scope
Architecture & Approach
Design decisions and rationale.
Constraints and compatibility notes.
Phases
[ ]
**
Phase 1:
- [ ] ** Phase 2:
** — Goal: < goal
Key Changes
Files/modules likely to change
Data/API/schema impacts
Verification Strategy
Lint/typecheck/tests/build commands
Manual checks if needed
Dependencies
New packages/tools (if any) with reason
Risks & Mitigations
Risk → mitigation
Open Questions
Items requiring user confirmation
phase-XX-
Phase XX:
Objective
Specific result for this phase.
Preconditions
What must already be true.
Tasks 1. Context: files/components to inspect or modify 2. Implement: exact change steps 3. Verify: commands/checks to run 4. Confirm: expected outcome
Verification
Commands:
< command 1
- < command 2
- Expected results: - < result
Exit Criteria
- Clear checklist that determines completion.
- Step 6: Review and Refine
- Before presenting the plan, verify:
- Paths are exact and consistent
- Phase order is logical
- Tasks are actionable (no vague steps)
- Verification is defined for each phase
- Risks/assumptions are explicit
- Plan is executable without hidden context
- Then present for user review.
- If multiple viable approaches exist, present options and ask for one of:
- Validate
-
- refine via additional clarifying questions
- Confirm
- approve current plan for execution
Iterate until confirmed.
Step 7: Handoff
When approved, end with:
Plan
/SUMMARY.md is ready. Use /clear and then /execute-plan /SUMMARY.md to execute it. Rules Never automatically implement or execute the code change in the same session, or ask user for execution right now, always finished when completed planning and ready for user review. Prefer explicit file paths and concrete commands Align with project standards and existing architecture Ask clarifying questions when uncertainty affects execution safety Keep plans self-contained and deterministic