verification-before-completion

Verify before completion requires running the actual proof command, reading its full output, and matching the reported state to the verification results before making any success claims. This enforces an evidence-first gate function for engineering tasks.

To verify code readiness before opening a pull request, execute the full proof command for your changes, review the complete output and exit code, and confirm the results match your completion claim before asserting the work is done.

Build validation requires identifying the verification needed, running the full command, reading the output and exit code, verifying results against your claim, and only then reporting the status. This gate function prevents false fixed or done claims.

Yes, verification before completion applies to CI pipelines and regression checks by requiring fresh evidence from running tests, linting, or builds before any satisfaction statement. It covers standard engineering workflows including readiness to commit or open PRs.

AI agents may claim a bug is fixed without showing test output because they skip the verification gate. To stop this, require the agent to execute the actual proof command, display complete output, and match results to the claim before confirming completion.

You should not skip verification before claiming completion when a task involves tests, linting, builds, or regressions. If no proof command can be executed to generate fresh output evidence, the verification gate cannot validate the completion claim.