verification-before-completion

Use gate-driven verification workflows to require running validation commands and analyzing fresh outputs before declaring success. This enforces evidence-based completion claims and prevents premature status updates across code changes, tests, and task deliveries.

Gate-driven verification is a workflow that mandates running verification commands and analyzing fresh results before allowing any completion claim. It ensures evidence-first reporting by attaching verifiable results like logs and test outputs to status updates.

Make completion claims auditable by enforcing structured prompts and checks that require fresh verification evidence before status updates. This sustains accountability during PRs, deployments, and handoffs by validating code changes, tests, and builds.

Yes, you can use this verification workflow for both pre-release checks and project management task tracking. It applies across code changes, tests, builds, and task deliveries to validate status before PR submission or marking tasks done.

The best way to prevent premature completion claims is implementing a gate-driven workflow that requires running a full verification command suite and reporting fresh results. This ensures evidence-first reporting and auditable outcomes before any success declaration.