verification-before-completion

To enforce verification before claiming task completion, you must identify the appropriate verification command, run it, and read the full output to ensure progress updates are backed by fresh evidence. This process discipline prevents premature status claims.

The best way to require PR readiness evidence is to implement a verification gate that runs CI checks and tests, documents the results, and only reports success after inspecting the verifiable output. This prevents dishonest or premature completion statements.

A verification gate for task handoffs works by requiring the execution of verification commands and inspecting their full output before any success is reported. This ensures that all progress claims are strictly backed by fresh, verifiable results.

Yes, you need to run tests or appropriate verification commands and read their full output before marking a software development task as done. You must record and present this evidence to support any claims of successful completion.

You should prevent premature completion claims in CI workflows to ensure that progress updates and PR merges are strictly backed by fresh verification evidence. This governance practice maintains quality assurance by requiring verifiable results before any success is asserted.