verification-before-completion

To prevent declaring completion without verifiable validation results, you must run explicit validation commands, review full outputs, and attach concrete evidence like logs or test results before marking tasks as done.

To enforce an audit trail in CI PR gating workflows, require running validation commands, collecting evidence such as test results, and documenting outputs to meet completion criteria before approving pull requests or releases.

Verification before completion in software quality assurance is the practice of backing every claim of done with concrete validation outputs and logs, ensuring proof-backed decisions for reliable releases and tracked issues.

Yes, you can use this validation approach for release checks and PR reviews. It applies directly to CI workflows and release gates by enforcing explicit commands and full output review to meet completion criteria.

Before marking work as complete, you need to attach concrete validation evidence such as logs, test results, and screenshots to support claims and ensure proof-backed decisions meet the defined completion criteria.

Declaring completion without evidence leads to unreliable releases because untracked issues bypass quality assurance checks. Enforcing verifiable validation results and collecting logs ensures proof-backed decisions before marking tasks as done.