verification-before-completion

To verify task completion claims, run explicit verification commands like automated tests and lint checks, collect fresh evidence from the outputs, and analyze exit codes and logs before publishing a final success claim.

Evidence-first verification is enforced by running verification commands on completed builds, analyzing the results and diffs to validate success criteria, and requiring command logs to support any completion statements before they are published.

Workflows allow premature success claims when explicit verification steps are missing, which this process solves by enforcing automated test execution and output analysis to collect fresh evidence before allowing any completion statements.

To stop premature completion statements, implement a discipline that prohibits success claims until automated tests are executed, exit codes are validated, and fresh command results are attached as evidence to support the final claim.

Yes, this verification process works with standard CI logs and exit codes by explicitly analyzing them to validate success criteria, ensuring that every completion claim is backed by fresh evidence collected directly from the command outputs.

You need to run automated verification checks before asserting task completion whenever a task reaches its final stages, ensuring that automated tests, lint checks, and build outputs are collected as evidence to prevent dishonesty and drift.