Create or update specs/{feature}/plan.md by turning an approved spec into one execution-ready document with key technical decisions, phased tasks, IDs (T001...), parallel candidates (P), story linkage, TDD-oriented bite-sized steps, and Definition of Done per phase. Use this skill whenever someone wants to translate a spec into concrete implementation work without maintaining a separate execution-design file, create a structured task checklist for a feature, add DoD to task phases, or create/update plan.md. This follows spec-specify and precedes spec-implement in the spec-driven workflow. Don't use for general to-do lists or project management outside the spec workflow.
Core principle: Write plans assuming the engineer has zero codebase context. Document everything they need: which files, what code, how to test, how to verify. No guessing.
Create or update specs/{feature}/plan.md as the execution source of truth, including technical context, key decisions, phased tasks, and completion conditions.
specs/constitution.md when presentspecs/{feature}/spec.mdspecs/{feature}/plan.mdspecs/{feature}/spec.md when backflow is requiredlanguage and shared rules from specs/constitution.md when present; otherwise infer from the available workflow documents and the user's own message. Ask only if still unclear, then conduct all subsequent interaction in this language.spec.md, extract user stories and constraints, and confirm spec approval state.
spec.md to be approved before generating the execution planreferences/plan-template.md.
spec-research instead of investigating inline- [ ] Txxx ...(P) for parallel candidates[USn] for story linkageDoD under each phase.
spec.mdspec.md status to draftstatus, summarystatus: draftstatus: approved when the plan is ready for implementationspec-implementspec-specifyspec-research(P) marks valid parallel work.spec-implementspec-researchplan.md path in the response