verification-before-completion

Prevent false completion claims by requiring fresh verification evidence before reporting success. Run full verification commands, evaluate outputs against success criteria, and report status with explicit evidence to guard against premature PRs and releases.

Verification evidence in code review is the fresh output from running full verification commands. It proves work meets success criteria before completion is claimed, ensuring claims are based on verifiable results rather than assumptions.

Verify outputs against success criteria by running full verification commands on your latest work, reviewing the command outputs, and reporting the status with explicit evidence to ensure tests pass and checks complete before merging.

Run full verification commands during a sprint before merging or releasing work. This ensures tests pass and checks complete, allowing you to base completion claims on verifiable results and produce evidence for audit.

Yes, the verification flow requires capturing evidence for audit. It guides users through a reproducible verification process, ensuring that fresh verification evidence is produced and reported before any completion claims are made.

Yes, this verification process applies to software development and review workflows where verification commands must be run and outputs reviewed. It prevents premature PRs and releases by enforcing verifiable results before marking work as complete.