verification-before-completion

Verify completion with fresh evidence by identifying the proving command, running it fully, reading the entire output and exit code, and only reporting success after confirmation. This enforces evidence-based completion for software development and QA checks.

Evidence-based verification requires executing verification commands, inspecting full outputs, and validating exit codes before making any completion claim. It prevents premature success reports by demanding unambiguous verification evidence across development, testing, and release stages.

Prevent premature completion claims by enforcing a step-by-step verification workflow before status changes. Require performing verification steps, collecting unambiguous evidence from command outputs, and validating exit codes before allowing any success claim.

Yes, verification-before-completion works across CI pipelines, QA checks, development, and release workflows. It is applicable to any task where progress claims must be backed by fresh verification evidence collected from command outputs and exit codes.

The best way to enforce code review verification is requiring a step-by-step workflow that executes verification commands, reads full outputs, validates exit codes, and attaches fresh evidence before any completion claim or status change occurs.

Claiming work as complete without verification is dishonest and risky because it lacks fresh verification evidence. Enforcing evidence-based completion by running verification commands and validating exit codes prevents inaccurate progress claims in software development and QA.