verification-before-completion

To prevent premature completion claims, enforce verification gating by running a command set to prove task status before committing or merging. This coordinates running verification commands and validates deterministic outputs to ensure work is fully complete.

Verification gating is the process of running a validation command set to prove task status before claiming completion. It supports quality assurance by enforcing strict validation against deterministic outputs and preventing unverified success declarations.

Collect evidence for audit-ready compliance reporting by capturing command outputs, exit codes, and relevant artifacts. This produces a verifiable trail of results for reviews, CI gates, and governance to meet risk and compliance requirements.

Yes, you can use verification evidence collection for CI gate enforcement. The process records fresh validation outputs and exit codes, producing an audit-ready trail of results that governance and CI gates can verify before merging changes.

Yes, verification before completion works without external dependencies. The Skill coordinates running validation commands and collecting outputs directly within your development workflow to enforce strict validation and record evidence independently.

Strict validation against deterministic outputs requires commands to produce consistent, repeatable results. If your verification commands rely on non-deterministic outputs or external state, the validation may fail or produce inconsistent evidence for completion claims.