verification-before-completion

To prevent premature claims of code completion, enforce a strict verification protocol requiring execution of specific commands and confirmation of their output before reporting success. This ensures evidence-based assertions are made upon task completion.

Evidence-based verification is a development principle requiring concrete output from test suites or linters as proof before declaring success. It enforces running mandatory verification commands to confirm status and prevent the accidental shipment of incomplete work.

To verify a bug fix is complete, run the relevant test suite or linter and confirm the output. This protocol demands evidence before assertions, ensuring you execute specific commands and validate their results before claiming the work is finished.

Yes, the verification before completion protocol applies to all stages of development and task management where work status is reported or committed. It requires adherence to the principle of evidence before assertions across the entire lifecycle.

Relying on assertions without verification commands leads to premature claims of work completion, compromising honesty and risking costly errors. Without executing tests to confirm output, you might accidentally ship broken or incomplete work.