verification-before-completion

To enforce verification before code completion, you must run specific commands, read their output, and confirm zero failures before asserting any task is done. This prevents premature claims by mandating evidence gathering protocols.

False completion claims occur when task management relies on rationalizations like "should work" instead of evidence. Preventing false claims requires running the test suite and verifying the actual output against assertions before declaring success.

The best way to prevent premature bug fixing assertions is to strictly require running verification commands and checking their output. You must verify results against claims and discourage common rationalizations for skipping the verification process.

No, you cannot claim a bug is fixed without running the test suite. Verification protocols require you to run the tests, confirm zero failures in the output, and gather concrete evidence before making any assertion of success.

To verify code passing status without trusting agent reports, you must independently run the verification command and read the actual output. Discouraging common rationalizations ensures you rely on gathered evidence rather than assumptions.

Skipping quality assurance before completion leads to premature claims of work done, allowing costly errors to slip through. It removes the strict protocol of reading command outputs and verifying results, undermining honesty in development.