writing-plans

A TDD-ready implementation plan is a structured roadmap that breaks complex features into granular tasks, mandating failing tests before code implementation to ensure architectural clarity and software reliability.

To break down complex software features, generate a structured plan that divides overarching architecture into bite-sized, 2-5 minute actionable steps, ensuring systematic documentation and clear execution instructions for subagents.

Yes, test-driven development planning requires strict adherence to DRY and YAGNI principles to prevent code bloat, ensuring the generated architectural workflow only includes necessary components for reliable implementation.

The best way to enforce a test-driven workflow is using a structured planning skill that mandates the creation of failing tests prior to implementation, providing a step-by-step execution roadmap for engineers and subagents.

Yes, this structured planning approach applies to complex feature development requiring granular task breakdown and systematic documentation, guiding engineers through architecture design and test implementation for large-scale tasks.

You should avoid generating granular task breakdowns for simple modifications that do not require architectural clarity, TDD workflows, or systematic documentation, as the overhead of 2-5 minute step generation is unnecessary for trivial updates.