tdd-engine

Test-driven development orchestration coordinates RED, GREEN, and conditional REFACTOR phases to guide task-card driven implementation workflows. It applies phase-specific prompts and controlled state transitions to deliver complex features reliably without losing test coverage.

Red-green-refactor cycles for parallel sprint tasks are managed through adaptive routing between standard, light-dispatch, light-inline, and prototype-inline execution modes. This approach preserves serialization rules for refactoring while allowing independent tasks within the same sprint group to proceed.

Adaptive execution routing selects between standard, light-dispatch, light-inline, and prototype-inline paths based on task size and risk. It applies phase-specific prompts, acceptance criteria handling, and test command selection to control state transitions during test-driven development.

Yes, this test-driven development workflow operates without external dependencies. It uses internal references to manage phase-specific prompts, acceptance criteria handling, and test command selection for task-card driven implementation workflows requiring reliable delivery.

The conditional refactor phase triggers during test-driven development after the GREEN phase produces the smallest passing implementation. It evaluates whether refactoring is required based on the task card's acceptance criteria and the current state of the implementation.

Test-driven development implementations lose context during phase transitions when lacking controlled state transitions and phase-specific prompts. This orchestration engine enforces strict RED, GREEN, and REFACTOR state management to preserve test coverage and context throughout delivery.