verification-before-completion

To prevent premature claims of code completion, enforce a strict verification protocol that requires executing test suites and reviewing command outputs before asserting any success status or expressing satisfaction.

Evidence-based verification is a protocol requiring command execution and output review before making any success claims, ensuring all status updates and task sign-offs are backed by fresh, factual results rather than assumptions.

To verify a bug fix before declaring it resolved, re-run the specific scenario that originally produced the bug and confirm through the command output that the failure no longer occurs.

Yes, you can use command output review to reduce shipping errors by catching incomplete or broken work early, ensuring mandatory test runs and build outputs confirm zero failures before committing code.

You need to apply mandatory verification protocols at all stages of development and task completion, specifically before committing code, declaring bugs fixed, or providing any status updates and task sign-offs.

Relying on assertions without execution evidence limits accuracy and honesty in reporting, leading to premature claims of work completion that risk shipping incomplete or broken code without catching issues early through fresh verification.