verification-before-completion

To enforce verification before merging a feature branch, run full verification commands and attach fresh outputs as evidence before status changes. This skill validates outputs against criteria and reports success only when evidence confirms the claim.

Verification before completion is a quality-assurance protocol that prevents premature success claims by enforcing fresh verification evidence. It ensures auditable evidence and reproducible results by evaluating command outputs against criteria before status changes.

Prevent unverified success claims during code reviews by enforcing a step-by-step verification protocol that runs full verification commands and evaluates outputs against criteria. This skill generates a traceable evidence log before reporting success.

This verification workflow does not require any specific testing frameworks or dependencies. It applies broadly to development workflows, tests, and deployments by requiring a full verification command and evaluating its output against your criteria.

The best way to ensure quality assurance with traceable evidence is to enforce a verification protocol that generates an evidence log and validates outputs against criteria. This prevents premature completion claims by requiring fresh verification before status changes.

You need to enforce fresh verification evidence in deployment workflows whenever success claims must be substantiated with verifiable outputs. This prevents premature completion claims by requiring a full verification command and evaluating its output against criteria.