ZES-writing-plans

To create a test-driven implementation plan, you generate a structured Markdown document that enforces TDD principles, breaking down complex features into granular 2-5 minute actionable steps with explicit file-path mapping and commit points.

Task decomposition in software development planning is the process of breaking complex multi-step features into bite-sized, 2-5 minute actionable steps, ensuring engineers have a clear roadmap with explicit architectural boundaries before writing any code.

You enforce TDD and DRY principles by generating a rigorous implementation plan that mandates the creation of failing tests before any implementation, ensuring code quality and clear architectural boundaries for every mapped file change.

Yes, this planning approach is specifically designed for multi-step feature development requiring clear architectural boundaries, applying granular task decomposition and explicit file-path mapping to satisfy your TDD requirements.

Yes, structured implementation planning works without external dependencies, as it focuses on generating a Markdown roadmap that defines test cases and commit points rather than relying on specific frameworks or external components.

You need an implementation plan to solve the problem of disorganized or vague development tasks by enforcing a rigorous TDD-based planning process, ensuring every step has explicit file-path mapping and architectural boundaries before coding begins.