verification-before-completion

To enforce running tests before claiming code completion, apply a strict verification protocol requiring execution of test suites and review of fresh outputs before making any success assertions. This prevents false claims by mandating evidence before confirming task finalization.

The evidence before assertions principle in quality assurance mandates executing relevant commands and independently verifying automated tool outputs before reporting any task as complete. It combats dishonesty and inefficiency by preventing unverified claims that tests pass or builds succeed.

To prevent false success claims in software development workflows, enforce a strict completion protocol requiring developers to run specific verification commands and confirm zero failures before asserting work is finished. This stops unverified assertions like build succeeds without actual fresh evidence.

Yes, you can use this verification protocol for agent task finalization. It applies to any process involving status reporting by requiring adherence to evidence before assertions and independent verification of automated tool outputs before claiming completion.

The best way to verify automated tool outputs before status reporting is to enforce independent verification by running the relevant commands and checking their fresh output. This strict protocol ensures no premature claims of work completion are made without actual proof.