verification-before-completion

To prevent premature completion claims, enforce a strict verification process that requires running specific testing commands and reviewing their output before any task is marked as done.

The best way to verify a bug fix is to re-run the relevant test command and explicitly review its output, preventing false positives based on outdated assumptions or previous states.

You can enforce empirical evidence for quality assurance by mandating the execution of verification commands, ensuring that all completion claims are backed by fresh, empirical testing data.

Yes, process enforcement for task completion applies to scenarios requiring empirical evidence, such as running build processes and code testing, to validate success before finalizing tasks.

Claiming a task is complete without verification causes issues because it prevents false positives and avoids reporting success based on outdated information, which leads to costly mistakes and premature ticket closures.