red-green-tdd

The Red-Green-Refactor cycle is enforced through gate-based development with explicit entry criteria. It requires passing through Decompose, RED, GREEN, and REFACTOR gates sequentially, ensuring a deterministic, auditable process that prevents skipping essential design steps during code changes.

A gate-based TDD workflow is needed for unit and integration changes involving logic, state machines, validators, or algorithms. It applies across software projects whenever a feature, bug fix, or behavior change requires a deterministic, auditable process with documented Decompose, RED, GREEN, and REFACTOR stages.

To prevent AI agents from skipping the test-writing phase, use a hard-gate protocol that blocks progression until explicit entry criteria are met. This enforces a documented Decompose, RED, GREEN, and REFACTOR cycle, automatically triggering for any logic, state, or behavior change.

Yes, this TDD enforcement protocol applies to both unit and integration changes. It is explicitly designed for changes involving state machines, validators, algorithms, and complex decision logic across software projects, automatically triggering whenever these behaviors are modified.

Hard gates in a Red-Green-Refactor workflow act as strict, non-skippable barriers with explicit entry criteria, unlike optional guidelines. This gate-based approach ensures a deterministic, auditable process by mandating sequential progression through Decompose, RED, GREEN, and REFACTOR steps for any logic change.