writing-plans

To create an implementation plan, provide a feature spec to generate a structured document outlining files to touch, tests to write, and documentation to review. The plan is saved as a markdown file for review before coding.

Structuring tasks for TDD workflows involves breaking feature specs into actionable, bite-sized steps that define files to create, tests to write, and documentation to review. This approach enforces a deterministic, incremental delivery process.

Yes, this planning approach supports incremental delivery by breaking complex requirements into bite-sized tasks with defined milestones. It ensures alignment across iterations by structuring tests and documentation before coding begins.

You document files and tests by generating a concrete implementation plan that specifies files to create or modify, tests to write, and docs to review. The plan is pinned to a markdown file in your docs directory for traceable commits.

Yes, you can use this method in a dedicated git worktree to encourage thorough preparation and traceable commits. The generated plan provides a structured roadmap for implementation before you start modifying code.

You need a structured implementation plan when tackling complex, multi-step tasks before touching code. It helps outline files, tests, docs, and milestones, ensuring alignment and minimizing wasted work during development.