writing-plans

To create an implementation plan, break down the specification into structured tasks that explicitly list files to touch, tests to write, and documentation to check. This ensures a complete map of the work is established before coding begins.

The best way to plan complex tasks with TDD is to enforce DRY, YAGNI, and TDD guidance during the task breakdown phase. This keeps the plan minimal yet thorough by explicitly defining required tests before implementation starts.

Generate a task breakdown by mapping each specification requirement to explicit files to modify and tests to write. This structured breakdown provides a comprehensive map of touched files and documentation needs for the entire project.

Save implementation plans to a versioned directory like docs/plans using a date-stamped filename, such as YYYY-MM-DD-<feature-name>.md. This enables team sharing and provides clear traceability for project requirements.

Yes, you need a spec or requirements document before planning complex tasks. This skill applies to projects where engineers already have requirements and need a complete map of touched files, tests, and documentation generated from that baseline.

Yes, you can use this structured planning approach for multi-task projects without external dependencies. It operates independently to produce comprehensive, step-by-step implementation plans directly from your project specifications.