verification-before-completion

Skipping verification steps often leads to claiming work is finished without actual proof, causing inaccurate reporting. A strict verification gate prevents this by requiring test execution and output confirmation before any success assertion.

Preventing rationalization in quality assurance requires a framework that identifies and rejects common excuses for skipping verification. It enforces a strict sequence of identifying, running, and reading verification commands before marking a task done.

You can apply this verification protocol to agent delegation workflows and task management. It ensures accountability by mandating agents execute verification commands and provide objective proof before reporting task completion.

The best way to verify task completion before a pull request is to systematically run tests, check build logs, and confirm actual output matches expected requirements. This ensures objective proof validates the success claim.