verification-before-completion

Verification before completion means running fresh tests, linters, and builds to confirm success with explicit evidence—exit codes, test counts, and output logs—before declaring work complete. This prevents false positives and broken code reaching your repository.

Establish a gate function that identifies and executes verification commands, interprets their outputs and exit codes, and blocks completion claims until evidence substantiates success. This eliminates rationalization and ensures only validated work is presented.

Implement a strict process that requires running full verification commands—tests, builds, linters—and reading their outputs before any completion statement. Counters common excuses like 'should work now' by mandating evidence-based assertions.

Yes. Automate the verification gate to run tests, confirm build success, and validate requirement compliance before commits or pull request creation, ensuring only code backed by fresh verification reaches reviewers.

Claiming completion without fresh verification creates false positives, wasted rework, and eroded trust. Requiring explicit evidence—test results, build logs, linter reports—ensures only validated work moves forward and maintains team confidence.