verification-before-completion

To enforce verification before claiming completion, you must identify a verification command, execute it fully, inspect the outputs, and only declare success after validating the results as evidence.

A verification gate is a repeatable process requiring fresh execution evidence before status changes. It ensures honest reporting by demanding verifiable proof across PRs, builds, or deployments before any completion claims.

You prevent premature releases by requiring quality assurance checks that run full verification commands and attach their outputs as evidence before closing tasks, approving PRs, or deploying updates.

Yes, evidence-based completion applies directly to pull requests and deployments. It requires identifying a verification command, executing it, and validating the output before declaring any development workflow successful.

The best way to verify work before closing a task is following a verification gate: run the full verification command, review the output, validate the results, and claim completion only with fresh evidence attached.