superpowers:writing-plans

To create a TDD-ready implementation plan, decompose complex features into bite-sized tasks, define interfaces, and mandate failing tests before implementation code. This enforces a rigorous test-driven planning process before any code is written.

Decomposing software architecture involves breaking complex features into bite-sized, independently testable tasks with explicit file path mapping. This ensures high code quality, architectural clarity, and frequent commits during development.

Test-driven development planning works by generating a step-by-step checklist that mandates creating failing tests before implementation code. It maps out architecture and defines interfaces to ensure every task is verifiable.

Yes, you need to define explicit file path mappings and interfaces before writing implementation code. This architectural decomposition is required to generate step-by-step task tracking and ensure test-first steps for every task.

This planning workflow applies specifically to complex feature development requiring architectural decomposition, interface definition, and step-by-step task tracking. It may not suit simple tasks that do not need rigorous test-driven planning.

You should write failing tests before implementation code to enforce TDD principles and ensure every task is independently verifiable. This prevents disorganized development by mandating a rigorous test-first planning process.