verification-before-completion

To enforce verification before completion, you must identify a command that proves success, execute it, review the full output, and verify the result before asserting any claim. This process standardizes completion checks across development workflows.

An evidence-first reporting workflow requires all completion claims to be backed by fresh test or command output and exit codes. It prevents premature success claims by mandating that you run verification commands and review outputs before reporting pull request status.

To stop premature success claims in feature releases, implement a verification gate that requires documenting verification steps, executing commands, and reading fresh outputs before asserting success. This disciplined process collects evidence before any completion claims are made.

Yes, the verification gate applies to code changes, pull requests, and feature completions. It standardizes completion checks across development workflows by requiring fresh verification outputs and documented steps before any success claim is asserted.

The steps to verify code changes are identifying a command that proves success, executing the verification command, reviewing the full output, and verifying the result. Only after completing this end-to-end sequence can you assert completion.

You need to document verification steps before asserting success because claiming work is complete without fresh evidence is risky and unreliable. Documenting the execution and output review ensures all claims are backed by current verification results.