verification-before-completion

To prevent premature completion claims in software development, you must execute specific verification commands and confirm their output before declaring any task complete. This approach ensures honesty and integrity in your work products by requiring clear evidence from command outputs.

Evidence-based task verification is the process of running specific commands and confirming their output before claiming work is finished. It ensures success claims are supported by clear evidence, maintaining integrity across coding, documentation, and project management scenarios.

You verify work before completion by running designated verification commands and confirming their output to ensure code review integrity. This process provides clear guidelines for identifying, running, and verifying commands, requiring clear evidence before making any completion claim.

Yes, task management verification applies to ensuring the integrity and reliability of work products in coding, documentation, and project management scenarios. It requires clear evidence from command outputs before allowing any completion claim to be made.

Requiring command output evidence improves task management honesty by preventing the claiming of work as complete or fixed without proper verification. It enforces integrity by demanding clear evidence from verification commands before any success claims are accepted.

The limitation of using command verification for completion claims is that it strictly requires clear evidence from command outputs before allowing any success claim. If verification commands are not properly identified, run, and confirmed, the completion claim cannot be made.