verification-before-completion

Verifying task completion requires running required commands, reviewing outputs, and validating exit codes to generate fresh evidence before asserting success. This enforces a stepwise workflow ensuring honest reporting for software development tasks.

Evidence-driven verification means running tests and validations to produce fresh output confirming success before claiming completion. It protects quality by ensuring claims are backed by recently generated proof rather than assumptions.

Enforce fresh test runs before PR approvals by applying a stepwise verification workflow that requires executing commands, reading outputs, and confirming passing results. Only claim success if the generated evidence validates the work.

Yes, completion governance requires actively running validation commands and reading their outputs to confirm results. The workflow guides users through executing verifications and checking exit codes before authorizing any success claims.

The best way to ensure honest reporting during task handovers is to enforce evidence-driven completion checks. This requires running verifications, reading outputs, and confirming passing results before asserting that work is complete.

Claiming completion without validation is risky and misleading because it lacks proof of passing tests. Enforcing fresh verification before success claims protects quality by requiring evidence of actual results.