writing-plans

To create a test-driven implementation plan, decompose complex requirements into atomic, verifiable steps using TDD principles. This approach mandates explicit file mapping, defines failing test cases before implementation, and utilizes subagent-driven review loops to ensure technical consistency and code quality.

The best way to break down large development tasks is to decompose them into bite-sized, 2-5 minute actionable steps. This task decomposition process ensures each step is verifiable and mapped to explicit file structures and test definitions before code execution begins.

TDD enforcement improves code quality by mandating the creation of failing tests before implementation begins. This structured planning phase validates plans against specifications through iterative review loops, ensuring high-quality, maintainable software architecture.

Yes, you can use subagent-driven review loops to validate implementation plans before coding. This review process checks technical consistency against requirements and ensures file mapping and test definitions are correct before any development execution occurs.

You need to map out file structure and failing test cases for a new API endpoint during the planning phase before code is written. This TDD-based approach guarantees the feature is built correctly by defining verifiable steps and iterative validation upfront.