verification-before-completion

To prevent false completion claims during code review and release readiness, enforce a verification gate that requires executing commands, evaluating outputs, and reporting verifiable evidence before declaring success.

Verification before completion is a governance mechanism in software development workflows that requires objective evidence from testing and code review before allowing status updates like pull requests or releases to proceed.

Enforce evidence-based quality assurance by running prescribed verification commands, analyzing the outputs, and collecting objective evidence to back completion claims before creating or approving a pull request.

No specific testing frameworks or dependencies are required. The verification gate applies to existing software development workflows by guiding teams to run explicit verification commands and evaluate outputs.

The best way to ensure release readiness is backed by objective evidence is to implement a step-by-step verification gate that mandates running commands and reviewing results before committing or pushing work.

Requiring explicit verification prevents premature completion claims by forcing developers to execute verification commands and report verifiable evidence, ensuring no work is marked done without objective proof of success.