writing-plans

To break down complex software features into testable tasks, you generate a structured implementation plan that enforces test-driven development principles and decomposes large features into bite-sized, independently testable units. This prevents scope creep before coding begins.

TDD-based architectural decomposition is the process of mapping out software components and file paths while mandating a failing-test-first approach for every unit of work. You need it when scoping complex features to eliminate ambiguity before implementation starts.

To create a step-by-step implementation plan enforcing TDD, you generate a structured document requiring explicit file path mapping and granular verification for every code change. This mandates a failing-test-first approach for all decomposed tasks.

Yes, this planning approach works for subagent delegation by generating step-by-step plans that ensure every component is documented, tested, and ready for implementation. It provides the granular, independently testable tasks that subagents require.

The best way to scope new development mechanics without scope creep is to force structured, test-driven decomposition of complex features before any code is written. This requires explicit file path mapping and granular step-by-step verification for every change.

You should not use test-driven implementation plans for simple modifications that do not require architectural decomposition or feature scoping. The strict TDD enforcement and granular verification overhead is designed for complex software development tasks.