verification-before-completion

To prevent false completion claims during code review, enforce an evidence before assertions protocol requiring fresh verification command output prior to declaring any task successful. This eliminates false positives by blocking completion statements without executed testing proof.

Bug fix verification fails without running testing commands because assumptions replace evidence, creating false positives. Enforcing execution of verification commands and reviewing their output ensures any passing status or completion claim is backed by fresh, concrete proof.

The best way to enforce process enforcement for honest work completion claims is applying an Iron Law protocol: no completion claims without fresh verification evidence. This mandates running and reviewing verification commands before any success assertion is made.

Yes, you can use automated verification for agentic workflows to stop premature task completion. By mandating the execution and review of verification commands prior to any completion statement, the protocol ensures all success assertions are verifiable and honest.

This verification protocol works for general software development, task management, and agentic workflows. It applies framework-agnostic process enforcement by mandating verification command execution and output review before any completion or passing status is declared.

You should never rely on assumptions for quality assurance and code review when claiming work is complete. Always execute verification commands and review their output to ensure zero failures before stating a bug fix is confirmed or all tests pass.