the-controller-verification-before-completion

To prevent premature task completion claims, you must enforce a strict verification process that runs specific validation commands and analyzes their full output and exit codes before asserting success.

Verifying code changes before committing requires executing mandatory validation commands, such as linters or builds, and confirming tangible output as evidence to prevent premature pull request creation.

Mandatory verification in agile development is a strict process requiring demonstrable proof of work state, enforcing the execution of specific validation commands before any claims of task success or completion are made.

To enforce evidence-based claims for bug fixes, you must re-run the relevant test case, analyze the full output, and confirm the passing exit code as tangible proof before declaring the bug fixed.

No, this verification process does not require specific dependencies or testing frameworks. It mandates running validation commands and checking their output and exit codes, regardless of the tools used.

The best way to ensure agents claim success only after demonstrable proof is to enforce a strict verification process requiring execution of validation commands and confirmation of evidence before any assertion of status.