verification-before-completion

To enforce verification before reporting task completion, identify a specific proving command, run it fully, parse the output, and confirm the evidence before asserting any success claim.

Claiming work as complete without verification causes problems by creating false success claims that are dishonest and waste time, leading to false positives in PRs, releases, and status updates.

The best way to prevent false positives in PRs and releases is to require fresh verification results by running a full verification command and confirming its output before declaring any task completion.

Yes, you can apply a clear, policy-driven checklist to any completion claim to improve trust and accountability by ensuring evidence-backed updates during code reviews and QA handoffs.

Yes, you need to identify the verification command for the task, run it fully, review the output, and only then claim success with evidence to ensure honest reporting.

You need to apply evidence-backed reporting for code reviews, PRs, QA handoffs, and status updates whenever a task completion claim is made to ensure honesty and prevent false success claims.