verification-before-completion

To enforce verification before claiming completion, you must run the relevant verification commands, evaluate the fresh output against success criteria, and document the results as evidence before asserting any work is done.

Reporting completion without fresh verification evidence causes workflow failures because it relies on outdated results or assumptions, skipping the objective validation needed to confirm outcomes in quality-assurance and release-readiness workflows.

The best way to prevent premature completion claims in CI/CD pipelines is to implement a gate function that executes verification commands fully and validates fresh output before any completion status is reported.

To document evidence when asserting task completion, run the required verification commands, capture the fresh output, verify it meets your success criteria, and provide that documented evidence alongside your completion claim.

No, you cannot use previous test results to verify code review readiness. You must execute verification commands to produce fresh output and evaluate it against success criteria before declaring any task complete.

Common failures when verifying outcomes include relying on outdated results, skipping full verification command runs, and asserting success without producing or evaluating objective fresh evidence against defined criteria.