verification-before-completion

Verify completion with fresh evidence by running verification commands, reading full outputs, and reporting status only after confirming results. This enforces a verification-first workflow before asserting work is complete.

A verification-first workflow requires running fresh validation commands and reviewing their outputs before claiming any task is complete. It prevents premature status updates by ensuring all tests, lint, and build steps pass with current evidence.

Prevent premature completion claims by enforcing a reproducible process to run verification commands and inspect outputs. You must confirm fresh results and back your completion status with evidence before posting updates.

Yes, this approach applies to software development, testing, and QA workflows where claims of completion must be backed by fresh outputs. It enforces running validation commands and reviewing full outputs for governance.

Asserting completion without fresh validation risks dishonest or premature status updates. Without running verification commands and reading their full outputs, you lack the reproducible evidence needed to confirm results.