verification-before-completion

To enforce verification before completion, identify the required verification command, run it fully, read the output, and validate the claim against concrete evidence to prevent unverified work from being marked as done.

Evidence-based verification in PR workflows is the process of running validation commands and evaluating their outputs for accuracy before claiming success. It satisfies guardrails by documenting failures and preventing premature completion claims.

You can prevent premature completion claims during code review by applying gate-based verification that requires running the necessary checks and reviewing the full output before any task handoff or success assertion is made.

When verification command output does not confirm success, you must document the failures as guarded disclosures to prevent false positives, ensuring the task is not incorrectly marked as complete.

Yes, gate-based verification can be applied across various development workflows including code reviews, PRs, and task handoffs to ensure evidence is gathered and reviewed prior to declaring any work done.

No specific dependencies are required to implement rigorous verification checks. The process applies standard verification commands and output evaluation to validate task completion claims within your existing environment.