writing-plans

To convert a project specification into an implementation plan, you provide the spec to generate a step-by-step task breakdown. This process yields bite-sized tasks, affected files, and testing steps for structured software execution.

A TDD-aligned task breakdown structures implementation steps by enforcing tests-first planning and frequent commits. This workflow ensures traceable progress by defining explicit test instructions and commit milestones before code context is established.

Yes, you can automate saving documentation-ready plans by exporting the generated task list to a standardized markdown file. The plan is archived to the docs/plans directory using a YYYY-MM-DD-<feature-name>.md format for easy reuse.

No, you do not need an existing codebase to generate a development plan. This planning approach specifically applies to software engineering tasks where a spec exists but code context is minimal, guiding teams through decisions and milestones.

The best way to structure milestones and file instructions before coding is using a standardized plan document template. This output explicitly defines task, file, test, and commit instructions, reducing ambiguity and guiding execution.