verification-before-completion

To prevent false completion claims, this approach requires running the exact verification command and checking fresh exit codes, command output, and failure counts before marking work as done.

A verification gate requires running the exact command that proves a claim, checking fresh command output and exit codes to prevent false success statements before opening pull requests or committing code.

To stop false success claims when running tests, require fresh verification output that checks exit codes and failure counts before declaring tasks finished, ensuring evidence exists for the success statement.

Yes, verification before completion works with CI pipelines by checking fresh command output, exit codes, and failure counts to ensure evidence exists before marking tasks as done.

The limitation of requiring fresh verification output is that it strictly prevents success claims without running the exact proof command, which may block task completion if verification commands fail or produce errors.