verify-before-complete

To enforce verification before completion, you need a strict gate that requires fresh evidence in the current message. This ensures verification commands run immediately after code changes, preventing stale confirmations when marking tasks or milestones done.

Blocking pull requests without recent test results requires enforcing a verification gate before creating commits or PRs. This process mandates executing verification commands and reporting fresh output immediately after making code changes to validate the outcome.

Stale completion claims happen when teams rely on session history instead of fresh evidence. Requiring verification output in the current message after code changes eliminates this issue, ensuring that any claim of done is backed by newly produced results.

Yes, a verification gate applies across code commits, pull requests, task milestones, and project status updates. It ensures that every time a claim of done is made, fresh evidence is produced by executing specific verification commands and reporting the results.

Verifying project completion involves a repeatable process: identify the claim, pick the exact verification command, execute it, and report the results. This maintains delivery discipline by ensuring evidence is freshly produced after each relevant change.

Avoid using an automated evidence gate when you cannot execute fresh verification commands in your current environment. The process requires producing new output immediately after changes, so it is unsuitable if your workflow prevents running the necessary validation steps.