verification-before-completion

To enforce evidence-based verification before code release completion, run fresh verification commands, validate their outputs, and report status claims only with attached evidence. This prevents unverified completion claims during releases.

The best way to prevent unverified completion claims during PR reviews is to require running fresh verification commands and validating outputs before declaring work complete. This ensures honest status updates backed by evidence.

To collect and report verification evidence for task handoffs, run fresh verification commands, validate the outputs, and report completion claims with that evidence. This guides evidence collection to ensure honesty in status updates.

Yes, you can use automated verification for quality assurance before completion by enforcing fresh command execution and output validation during releases and PRs. This prevents unverified completion claims and misleading success signals.

Claiming work as complete without verification invites defects and misleading success signals because it skips running fresh verification commands and validating outputs. Enforcing evidence collection prevents these unverified completion claims.

Yes, verification before completion works with CI-CD pipelines and code reviews by applying evidence collection during releases, PRs, and task handoffs. It enforces running fresh verification commands and reporting results with evidence.