verification-before-completion

To enforce test verification before claiming completion, apply a strict five-step protocol: Identify, Run, Read, Confirm, and Claim. This ensures all success statements are backed by fresh evidence from executed commands like test runners.

The best way to prevent false positives in task completion reporting is to require evidence-based validation. You must execute relevant verification commands, read their output, and confirm the results before making any success claims.

To validate command output before reporting a task as passing, run the relevant build or test commands, read the output, and confirm it meets specific criteria. Only then can you claim the task is passing.

Mandatory verification requires running relevant validation commands such as test runners, linters, or build tools. You must execute these tools, read their output, and confirm the results before claiming any work is complete.

To verify a bug fix before claiming success, follow a five-step process: Identify the verification command, Run it, Read the output, Confirm the fix is validated, and then Claim completion with the evidence backing your statement.

Claiming task completion prematurely causes reporting issues because it promotes false positives. Without strict verification through executed commands and output analysis, success statements lack the fresh, direct evidence needed for accurate status reporting.