writing-plans

Generate an implementation plan by transforming a spec into a task-by-task roadmap. The plan outlines files to touch, tests to write, and documentation to update, saving the output to docs/plans/YYYY-MM-DD-<feature-name>.md for clear deliverables.

Structure TDD steps and frequent commits by enforcing a consistent plan format with a header and Task N outline. This sequence integrates test-driven steps and staged commits for code, tests, and docs, ensuring full traceability and reproducibility.

Yes, implementation plan generation supports a dedicated Git worktree environment. It produces file and directory maps directly suitable for worktree setups, ensuring isolated development and version control without context overlap.

Outline files to touch and tests to write by creating a comprehensive implementation roadmap before coding. This provides engineers with zero context a bite-sized sequence of tasks, detailing exact file modifications and required test coverage.

Yes, plan generation operates without external dependencies or components. It relies solely on a provided feature spec or requirements document to produce the structured markdown plan with mapped tasks and commit guidance.

Convert requirements into a task-by-task plan to reduce ambiguity and rework before coding. This structured planning approach breaks down specs into clear deliverables, testing protocols, and documentation updates, saving plans as dated markdown files.