tdd-strict

The strict Red-Red-Green-Refactor cycle is a Test-Driven Development protocol requiring tests to fail initially and pass only after writing minimal, necessary code, ensuring high-assurance reliability by eliminating speculative code.

To prevent dead code and lucky passes, enforce a strict TDD cycle that requires documenting expected test failures and mandates the deletion of any code not directly required by a failing test.

Implement a strict TDD cycle by documenting the expected error before writing code, confirming the test fails as expected, and then writing minimal code to make it pass before refactoring.

Use a strict TDD protocol when implementing sensitive features or fixing critical bugs where absolute certainty in code correctness is paramount and high-assurance reliability is required.

Yes, strict TDD requires explicit documentation of expected test failures before writing code to eliminate code hallucinations and ensure high-assurance reliability.