tdd

Test-driven development automation enforces disciplined RED, GREEN, and REFACTOR cycles by isolating the test writer from the implementer using multi-agent context boundaries. It triggers on prompts like 'implement with TDD' or '/tdd <feature>' to guide feature creation.

TDD automation supports framework adapters for Jest, Vitest, pytest, Go test, cargo test, RSpec, and PHPUnit. These adapters load framework-specific prompts to ensure the test-driven workflow integrates smoothly across multiple languages and testing environments.

Multi-agent context isolation in test-driven development separates the test writer from the implementation details to prevent leakage of implementation intent into tests. This boundary ensures tests validate behavior independently, enforcing stricter test-driven design.

You start an interactive test-driven development workflow by invoking the '/tdd <feature>' command. This triggers an orchestration phase flow consisting of setup, decompose, red, green, refactor, and summary, with per-slice approvals for structured feature delivery.

Automated TDD enforces strict checkpoints through its orchestration phase flow. It requires per-slice approvals during the setup, decompose, red, green, refactor, and summary stages, ensuring disciplined progression before moving forward in the development cycle.