verification-before-completion

To prevent premature claims of task completion, enforce an evidence-before-claims protocol that mandates running verification commands like tests or builds and analyzing their output before asserting any success.

Sufficient evidence to verify a bug fix requires running the relevant test case, confirming it passes, and checking that the original symptom is resolved before making any final success claim.

Claiming success before running tests causes quality assurance issues by propagating unverified states, which this verification protocol prevents by ensuring evidence always precedes positive assertions.

Identify red flags of unverified completion by recognizing common pitfalls and phrases that indicate a lack of verification, ensuring commands proving a claim are run and reviewed first.

Run verification commands for development task finalization at all stages, ensuring tests, builds, and linters execute successfully and their output is reviewed before any completion assertion is made.

Verification-before-completion applies to all stages of development and task finalization, enforcing a strict protocol that accuracy is confirmed through command output analysis before any success statement.