verification-before-completion

You enforce verification before completion by mandating that specific commands are executed and their output examined before any assertions of success are communicated. This protocol actively counters rationalizations for skipping verification steps.

The evidence before assertions principle requires running verification commands, examining their output, and presenting concrete results before claiming any task success or completion. It prevents premature declarations throughout the development process.

To verify test suite output before declaring a bug fix complete, run the linter and test suite, examine their actual output, and communicate the passing assertions with that evidence. No completion claims should be made without fresh executed verification.

Your code review process suffers from premature declarations when rationalizations lead to skipping verification steps. Enforcing a strict protocol that requires examining executed command output before communicating assertions actively counters these common red flags.

Yes, you can apply this verification protocol across all stages of software development and task completion. It universally prevents premature declarations by mandating executed command output before any success assertions are communicated.