test-driven-development

Test-driven development orchestrates RED-GREEN-REFACTOR cycles across isolated contexts to enforce test-first development. It solves the problem of maintaining disciplined phase boundaries and clean handoffs by validating transitions between phases using formal contracts and observable outcomes.

The best way to enforce strict phase boundaries during feature development is by orchestrating TDD cycles across isolated contexts. This approach uses formal handoff contracts and references to validate transitions, ensuring disciplined phase separation and predictable outcomes.

To start a test-driven discovery session, spawn a RED context targeting a specific unit of behavior. Then execute the GREEN and REFACTOR phases following the formal handoff contracts, validating each transition to maintain strict phase boundaries throughout the cycle.

Yes, you can use this TDD orchestration approach for handoff validation between development phases. It applies formal contracts and references in phase-handoffs documentation to validate transitions, ensuring observable outcomes and explicit handoffs between isolated contexts.

You should avoid using spawned contexts for test-driven development when your workflow does not require strict phase boundaries or formal handoff validation. If your development process lacks explicit phase separation or observable outcome requirements, this orchestrated approach adds unnecessary overhead.