verification-before-completion

To enforce verification before completion, identify a verification command that proves success, run the full command suite, read the output, and compare results against expectations. The skill ensures evidence-backed claims by gating status updates until proof is captured.

Claiming completion without verification leads to defective releases because it bypasses evidence-based validation. Without running verification commands and capturing proof, misinformation spreads and untested changes reach production, compromising software integrity and compliance.

The best way to automate compliance for PR sign-offs is implementing a repeatable governance process: identify the verification command, run it, read the output, verify against expectations, and only then claim success. This ensures traceability and truthfulness for deliverables.

To capture proof before a release, execute the verification command suite on your latest build, read the output to verify all checks pass, and record the evidence. This quality-assurance step guarantees only evidence-backed completions are marked as successful.

No dependencies or components are required to use this evidence-based completion workflow. The skill operates independently to enforce governance and quality-assurance by defining a repeatable process to identify, run, read, verify, and claim success.

You need an automated verification gate for deliverable sign-offs when truthfulness and traceability are critical, such as during software PRs, audits, or deployments. It prevents misinformation by requiring captured proof before any status is updated to complete.