test-first-enforcer

To enforce test-first discipline, configure a pre-tool hook that blocks production code edits unless related test files exist for the same sprint task, ensuring tests always accompany production changes for improved release reliability.

Test-first enforcement prevents fragile releases by blocking production code changes until corresponding tests are written within the same task. This mechanism ensures verification happens before implementation, improving traceability and reliability.

Yes, you can bypass test-first rules by using the /sprint:test-exempt command. This exemption requires documented reasons and generates logs for compliance review, ensuring traceability even when skipping tests.

To set up test-first compliance checks, integrate the pre-tool-use-test-first.sh hook with the dod-validator. This configuration inspects your production_paths and exemption rules to enforce discipline across active tasks.

Yes, test-first enforcement integrates with the dod-validator to verify test-first discipline across tasks. This integration ensures all production edits meet Definition of Done compliance through automated verification during active sprints.

Use a test-first exemption when a specific production code change legitimately bypasses test requirements. The /sprint:test-exempt command documents the reasons and logs them for compliance review during active sprint tasks.