verification-before-completion

To prevent false work completion claims before a code commit, enforce strict verification by running full test suites and build checks to gather concrete evidence, ensuring zero failures before asserting success.

Verification evidence in software development workflows is concrete proof of requirement compliance, such as a successful build exit code or zero test failures, collected immediately before marking a task or pull request as done.

Partial test checks lead to broken code in pull requests because unverified assumptions bypass strict workflow guardrails. Trusting agent success reports or skipping full test validation increases the risk of missed requirements and wasted rework.

Enforce test validation before marking a bug fix as done by applying a verification gate that identifies the correct test command, runs it fully, reads the output, and confirms requirement compliance before any success claims are made.

Yes, this verification gate works with agent task delegation. It applies strict validation rules to eliminate unverified assumptions, requiring delegated agents to provide fresh build checks and test results before reporting task completion.