verification-before-completion

To enforce test verification before task completion, mandate explicit verification command execution and output analysis for any status reporting. This prevents premature declarations of success in CI/CD workflows by requiring auditable proof of passing tests before claims are made.

An evidence before claims protocol requires running verification commands and analyzing their output before asserting any task success, correctness, or completion. It prevents false positives like assuming tests pass without running them, ensuring all success claims have auditable proof.

To prevent false positives when claiming a bug fix is complete, require explicit verification command execution and review the actual test output before reporting status. This prevents assuming builds succeed based on partial checks and mandates auditable proof of work.

To generate auditable proof of work for code quality, execute verification commands and analyze their output before reporting any task completion status. This protocol ensures all assertions of correctness are backed by explicit test evidence rather than assumptions.

Strict verification before completion integrates with existing TDD workflows by applying an evidence before claims protocol to all status reporting. It ensures test-driven development outputs are explicitly run and analyzed before any success assertions are made, preventing false positives.