writing-plans

To generate a TDD-ready implementation plan, you provide high-level requirements and the skill breaks them into granular, 2-5 minute actionable steps. It mandates failing tests before implementation, ensuring every file and commit is accounted for to prevent scope creep.

The best way to break down ambiguous development tasks is enforcing a rigorous planning phase that transitions high-level requirements into bite-sized tasks. This structured documentation ensures adherence to DRY and YAGNI principles before any code is written.

Test-driven development planning handles execution handoffs by providing a clear choice between subagent-driven iteration or parallel session execution. This structured documentation operates within a dedicated worktree to maintain clear, actionable engineering steps.

Yes, you can use structured implementation planning to prevent scope creep by ensuring every file, test, and commit is accounted for before coding begins. This rigorous, TDD-focused phase enforces DRY and YAGNI principles for high code quality.

You should not use a TDD-focused planning phase for trivial tasks that require immediate code changes without structured documentation. It is designed for complex software features needing granular, test-driven implementation plans and strict scope enforcement.