plan-tdd

To create a test-driven development plan, you provide project requirements and constraints to generate structured documentation. This produces a complete TDD blueprint that breaks the project into testable components, incremental testing cycles, and clear acceptance criteria.

A TDD development plan includes structured documentation artifacts specifying testing cycles and acceptance criteria. It generates tdd-development-plan.md, tdd-implementation-prompts.md, and testing-strategy.md files to guide incremental implementation.

You generate red-green-refactor prompts by inputting project requirements into a TDD planning workflow. The process outputs tdd-implementation-prompts.md, providing step-by-step prompts for each testing cycle to guide incremental development.

Yes, a structured TDD workflow applies to teams seeking repeatable development cycles across specification reading, blueprinting, and incremental implementation. It ensures test coverage and aligns implementation with project requirements through documented constraints.

The best way to blueprint testable components is using a test-first planning process that outputs a testing-strategy.md file. This approach defines required outputs, clear testing cycles, and acceptance criteria to ensure comprehensive test coverage.

No specific testing frameworks are required to generate a TDD implementation plan. You provide project requirements and constraints, and the process outputs framework-agnostic documentation detailing testing cycles, step-by-step prompts, and acceptance criteria.