verification-before-completion

Evidence-based task completion is enforced by executing specific verification commands and objectively analyzing their output before making any success assertions. This protocol prevents premature claims of success by requiring objective test or build outputs.

The best way to prevent premature success claims is to apply a strict verification protocol that requires running the full test suite and checking exit codes. This counters cognitive biases that lead to skipping necessary debugging and testing steps.

To verify test passes and build success, you must execute explicit verification commands and validate the objective output. This ensures technical accuracy and reliability by proving the code works rather than relying on partial checks or assumptions.

This verification protocol works directly for deployment preparation, debugging, and general software development workflows. It ensures technical accuracy by demanding command execution and output analysis before any task is marked as fixed or ready for production.

You should require explicit verification commands because assuming code works based on partial checks introduces reliability risks and cognitive biases. Strict command execution and output analysis guarantee technical accuracy and prevent rationalization before task completion.