verification-before-completion

Verification before completion enforces a mandatory protocol requiring specific validation commands and independent output review before any success claims. This prevents unverified status assertions and ensures technical accuracy in software workflows.

To stop rationalizing skipped testing steps, use a verification framework that identifies and blocks common excuses for bypassing validation. This enforces accountability by requiring test suite execution and output review before marking tasks done.

A verification gate in quality assurance workflows is a strict process mandating the identification, execution, and verification of commands before any success claims are made. It ensures technical reliability and prevents unverified task completion assertions.

Yes, you can use this verification protocol for agent-based task execution where state verification is critical. It applies directly to software development workflows and code reviews by enforcing mandatory validation commands before completion claims.

The best way to verify code review output before submitting a pull request is to systematically run the necessary test suite, ensure the linter is clean, and confirm the build succeeds using a strict verification gate protocol.

You should avoid using a strict verification gate protocol for trivial changes where running full validation commands provides no critical state verification value, as the overhead outweighs the reliability benefits for low-risk software modifications.