create-plan-tdd

To generate a structured TDD implementation plan, provide a task description or ticket reference to initiate automated wave-based task grouping. The system maps dependencies and creates wave groupings to enable concurrent work.

Wave-based task grouping in test-driven development organizes implementation tasks by dependencies to enable parallelization. It typically starts with a Wave 0 for infrastructure setup, followed by subsequent waves of concurrent tasks.

Yes, the TDD planning approach enforces RED, GREEN, and REFACTOR cycles for every task. It structures the implementation plan to strictly follow test-first development cycles before finalizing any wave.

Multi-persona reviews improve test-first development planning by applying diverse analytical perspectives before finalization. This review loop evaluates the generated plan artifacts for quality, dependency accuracy, and test coverage gaps.

Yes, you can parallelize development tasks using dependency analysis to structure concurrent work waves. The planning automation analyzes task dependencies and groups them into waves to maximize parallel execution safely.

A limitation of wave-based planning for test-driven development is the strict dependency on prior wave completion, meaning tasks with heavy interdependencies cannot be easily parallelized within the same wave.