sp-writing-plans

To turn software specs into implementation plans, provide your approved design requirements to generate a structured document detailing tasks, files to touch, tests to write, and milestones. The plan prevents scope creep by documenting assumptions and edge cases before coding.

The best way to plan a multi-step feature is generating a comprehensive implementation plan that lists file touchpoints, testing steps, and commit instructions. This approach documents edge cases and milestones, ensuring an executable workflow before you start coding.

Task planning for TDD workflows works by converting architectural decisions into bite-sized, executable tasks. It produces a dated plan document under docs/plans that aligns testing steps with milestones, ensuring implementation follows a structured, test-driven sequence.

Yes, you can use implementation plans for bug fixes, refactors, and infrastructure changes. The planning process applies to any multi-step software engineering task, generating executable task lists and documenting assumptions to prevent scope creep.

You generate a plan document with commit instructions by applying the planner to your spec. It automatically produces a structured file under docs/plans with a date-based filename, containing task lists, file touchpoints, testing steps, and commit guidelines.