verification-before-completion

To verify completion before a pull request, run the full test suite and build commands, inspect the fresh logs and artifacts generated, and report those specific outputs as evidence that the task is complete.

Running verification commands before claiming a release is ready prevents false completion claims by enforcing a gate where you must execute tests, read the actual outputs, and validate artifacts before declaring success.

An evidence-based verification workflow requires identifying and executing explicit test commands, inspecting the resulting logs and artifacts, and only making completion claims after validating fresh outputs from those runs.

Yes, this verification process applies to any software development workflow where completion claims require fresh evidence, enforcing explicit steps to execute commands, inspect results, and report findings before releases.

The best way to enforce explicit verification steps is applying a repeatable gate function that guides you to identify, run, read, and verify final commands and artifacts before making any success claims during your workflow.