tdd

End-to-end TDD orchestration reads an existing feature plan and creates ordered tasks across E2E, Backend, and Frontend phases. It coordinates RED/GREEN testing cycles automatically by spawning specialized implementation and review sub-agents to execute work without manual coding.

Outside-in development structures testing by progressing from E2E to Backend and Frontend phases. This approach validates external behavior first, then drives internal implementation, coordinating RED/GREEN cycles across each layer using specialized sub-agents to verify work.

You can resume a partially completed TDD session with existing tasks. The orchestration workflow detects prior progress and continues executing the feature plan, coordinating remaining RED/GREEN phases and spawning implementation sub-agents to finish the outstanding work.

A predefined plan is required before running outside-in TDD orchestration. The orchestrator validates plan presence upfront to structure dependencies across E2E, Backend, and Frontend tasks, ensuring sub-agents have a defined sequence to execute without manual coding.

TDD orchestration handles blockers by tracking friction during sub-agent execution. Instead of failing silently, it surfaces these friction points to the user for review, allowing you to identify and resolve constraints blocking the RED/GREEN development phases.

Automating feature plan execution without manual coding is done through agent-based TDD orchestration. It spawns specialized implementation and review sub-agents to handle the coding, sequentially executing E2E, Backend, and Frontend tasks while coordinating RED/GREEN testing phases.