verification-before-completion

Preventing premature completion claims requires running the relevant verification command, reading its output and exit code, and citing that evidence before asserting success in status reports or pull requests.

The best way to verify task completion before pushing a commit is to rerun the applicable test suite, capture the full output, and document the exact results before declaring the work done.

Documenting command run evidence involves executing the proving command fully, capturing the output logs, and explicitly recording any failures or successes before submitting the status report.

If a verification command fails, the task cannot be marked complete; the failure must be documented explicitly from the output and exit code before any further success claims are made.

Yes, it integrates into development workflows by inserting a verification gate that demands hard evidence from command runs before allowing satisfaction claims for commits, pull requests, or handoffs.