verification-before-completion

A verification gate prevents premature completion claims by requiring validated results and verifiable evidence. It enforces a checkpoint before commits, PRs, or releases, reducing risk in development workflows by ensuring tasks are actually finished.

To verify completion before a pull request, run full verification commands and record the results before asserting success. This validates outputs against success criteria and reports failure details, ensuring only verified tasks proceed to PRs.

The best way to prevent premature completion claims is enforcing a verification gate that requires running checks and gathering evidence before any success statement. This ensures all claims are backed by validated results across diverse projects.

Yes, you can use a verification gate to validate code review readiness for sprint demos. It runs verification commands, aggregates outputs, and evaluates success criteria, ensuring deployment readiness and reducing risk before presenting completed tasks.

When evidence does not confirm success during pre-commit validation, the verification gate reports the status with specific failure details. This prevents the completion claim from proceeding until the validated results meet the success criteria.