verification-before-completion

To enforce verification before completion, identify the required verification command, execute it fully, review the output, verify the results, and only then claim success with fresh evidence.

The process to prevent unverified success claims applies a step-by-step verification gate, requiring fresh verification commands and evidence gathering before finalizing tasks like tests, builds, or deliverables.

Yes, you can use this verification gate for build and test workflows. It applies to any tasks where deliverables are finalized and reported, requiring evidence-backed completion before success is declared.

The best way to ensure quality governance and stop premature completion claims is to define explicit gate criteria in your process, mandating that fresh verification commands run successfully before any success statement is made.

Claiming work as complete without verification causes process issues because it is dishonest and inefficient, leading to unverified success statements that bypass mandatory evidence gathering and quality governance checks.