implementation-planning
Author the mechanical <feature>.plan.md from approved requirement + overview-plan + analyzed. One section per step; final step is the E2E validation gate. No Severity column. Used by the software-engi
SKILL.md.claude/skills/implementation-planning/SKILL.md
GitHubImplementation planning skill
Mission
Author the mechanical implementation plan: concrete substeps with file paths and done-when conditions, one section per implementation step.
Owned artifact
docs/<feature>/<feature>.plan.md. Template: ~/.claude/templates/feature.plan.md.
Read scope
docs/<feature>/<feature>.requirement.md(BA's approved output).docs/<feature>/<feature>.overview-plan.md(Architect's canonicalStep A/B/…list).docs/<feature>/<feature>.analyzed.md(Architect's analysis incl. Step Severity table).docs/<feature>/<feature>.test.md(Tester'sE2E-ncases — implemented at the final step).- The plan template;
docs/architecture.md; projectcoding-rules+architecture-rules(context) + softdocs/narrative//docs/domain/viaproject-seams.
Procedure
- Read the approved requirement, overview-plan, analyzed, plan template, and relevant project rule skills.
- Write
docs/<feature>/<feature>.plan.mdmirroring the template. One section per implementation step fromoverview-plan.md(Step A,Step B, …) — same IDs, same order, no renaming. Each step lists concrete substeps with file paths, types/methods to create, and done-when conditions. - The final step of
plan.mdMUST be the E2E validation gate: a step that authors automated e2e tests from<feature>.test.mdand runs them via the project'stest-runneragent — done-when everyE2E-ncase is green. (Execution lives in thee2e-validationskill.) - No Severity column.
plan.mdis mechanical; per-step Severity lives inanalyzed.md(Architect, R7). Do not duplicate that table here. - Save via
Write. Hand off perpipeline-protocol: "Stage 2-plan complete. Awaiting user APPROVE on<feature>.plan.md. After APPROVE,status.mdis initialized mechanically and/workflow:step-start <feature>begins implementation."
Boundary
Does not author requirement.md / overview-plan.md / analyzed.md, author or modify the Step Severity table, flip [X], or write status.md. Full contract: pipeline-protocol.