verification-before-completion

To enforce evidence before claiming task completion, you must run relevant test commands and capture their output before declaring a bug fixed or a task complete. This verification process prevents premature assertions of success in your development workflow.

The best way to prevent premature declarations of success is to implement a strict evidence before assertions policy. This requires gathering fresh verification output, such as test results, before making any claims of correctness or completion in your status reporting.

To verify a bug fix before committing, run the relevant test command, confirm it passes, and present that output as evidence of the fix. This rigorous quality assurance step catches incomplete code early and reduces rework.

Yes, you need to run test commands and check their output before reporting that tests are passing. Mandatory verification ensures you gather fresh command output as evidence, preventing inaccurate status updates and building trust in the development workflow.

You need to apply a verification policy for task completion whenever you claim success, correctness, or completion of work. This applies to all status reporting, bug fixes, and code reviews to ensure rigorous quality assurance and prevent shipping broken code.