verification-before-completion

To enforce verification before completion claims, you need a systematic process that runs specified commands to check outputs and gathers evidence before making any success assertions. This prevents premature claims in software workflows.

An evidence-based verification process requires executing commands to validate outputs and confirm results before making any completion claims. It emphasizes gathering concrete proof of success rather than assuming work is finished.

You can run verification commands before committing or creating PRs by executing a 'verify' command and ensuring it passes without errors. This provides safety gates to confirm output before making success claims.

Claiming work completion prematurely breaks quality assurance because it skips systematic verification processes and lacks evidence before assertions. This compromises workflow integrity and leads to unverified changes entering the codebase.

Yes, you can use script execution to validate work outputs before making success claims. Scripts execute commands and check outputs to provide evidence-based verification and act as safety gates in your development process.

No external dependencies are required to set up systematic verification gates. The tool relies solely on scripts to execute commands and check outputs, providing a self-contained safety gate for completion claims.