ss-sdd-writing-plans

You convert an approved specification into a TDD implementation plan by rendering the spec into a plan.md file containing bite-sized tasks organized by user story with concrete tests, code, and commit steps.

Breaking down software specifications into executable TDD tasks involves decomposing the spec into 2–5 minute bite-sized tasks organized by user story, ensuring each task includes concrete file paths, commands, and test steps.

An approved SDD specification is required before writing an implementation plan, because the plan generation applies after spec commitment to support MVP-first delivery without re-deriving intent.

You cannot use placeholders in your TDD implementation plans, as the plan generation enforces hard constraints that prohibit placeholders and forbidden diagram syntaxes to prevent downstream implementers from guessing intent.

You ensure implementation plans include concrete file paths and test commands by applying safety guardrails during spec-to-plan rendering that enforce hard gates requiring exact file paths and prohibiting ambiguous placeholders.

An implementation plan needs to load project context like architecture and ADRs to align the generated TDD tasks with existing project constraints and definitions via optional context loading mechanisms.