writing-plans

To create a test-driven implementation plan from a design document, you need to decompose requirements into concrete file paths, test scaffolding, and commit-ready steps. This process traces decisions from the design doc through a Red/Green/Refactor flow.

Breaking down software requirements into file paths and tests involves inspecting existing codebase patterns to generate a traceable, multi-step roadmap. This ensures explicit task decomposition and aligns tests with specific code changes for reviewers.

Generating an implementation plan does require the ability to inspect existing patterns. Accessing these patterns allows the plan to specify concrete file paths, accurate test scaffolding, and commit steps tailored to the target feature.

You can outline a Red/Green/Refactor flow for multi-step engineering tasks by structuring the implementation plan around test scaffolding. This encourages test-driven development by defining failing tests first, implementing code to pass them, and then refactoring.

Linking design docs to code changes for traceable reviewer decisions requires mapping explicit task decomposition steps directly to file paths and commits. This provides a clear roadmap connecting the original requirements to the final implementation.