redsub-plan

To generate a TDD implementation plan, define the feature scope and the Skill will output a detailed task breakdown. It enforces a Test-Driven Development structure, mandating a failing test, implementation, and passing test for each 2-5 minute step.

The best way to break down development tasks into bite-sized steps is enforcing task granularity of 2-5 minutes. This approach ensures each step includes a specific failing test, the exact code implementation, and a passing test verification.

Yes, you can get an implementation plan with exact file paths and complete code snippets. The generated plan is entirely self-contained, providing commands with expected outputs to ensure zero context is needed during execution.

Test-driven development planning works without needing additional project context because the output enforces zero context documentation. Plans include exact file paths, complete code snippets, and commands with expected outputs for immediate execution.

You should use a TDD structure for task breakdown because it enforces test-first development with strict 2-5 minute task granularity. This ensures every implementation step is verifiable, reducing errors and maintaining steady development workflow momentum.

A limitation when generating bite-sized implementation plans is that the feature must be divisible into strict 2-5 minute TDD cycles. Highly exploratory tasks or features lacking clear test boundaries may not fit this rigid failing-test-implementation-passing-test structure.