verification-before-completion

To enforce verification before completion claims, apply a strict sequence: IDENTIFY the task, RUN the full verification command, READ the output, and VERIFY exit codes before updating status. This prevents premature completion claims across PR workflows.

The verification process requires calling the full verification command, parsing exit codes, and requiring explicit confirmation before updating status. You run the sequence, review the full output, and only claim success if results prove the claim.

Yes, this verification pattern applies across code changes, tests, linting, builds, and policy enforcement for deployment gates and release workflows. It ensures outputs align with expectations before any status is updated.

No dependencies are required. The approach functions as an advanced internal reasoning pattern that parses exit codes from your existing verification commands, requiring explicit confirmation before allowing any completion claims.

Completion status updates prematurely when evidence and verification are not enforced. Implementing a guardrail that parses exit codes and demands explicit confirmation prevents status changes until tests, linting, builds are proven successful.