verification-before-completion

To enforce verification before completion, run fresh verification commands, evaluate their outputs, and attach the results as evidence prior to updating any task, code, or PR status.

Evidence-based completion is a quality-control process that prevents unverified claims by requiring explicit verification commands to be run and their outputs confirmed before any success is declared.

To stop unverified claims during sprint finalization, apply a verification gate that executes necessary checks and reports verified results to substantiate completion before any status update is made.

Yes, you can use a verification gate for general task workflows outside of code because the skill applies to tasks and PR workflows where running verification commands and attaching proof prevents misinformation.

The best way to attach proof of quality control before a release is to execute a step-by-step verification sequence, compare the outputs, and report the verified results to substantiate completion.

Claiming work is complete without fresh verification leads to faulty releases because it allows unverified claims to bypass quality control, causing misinformation and faulty releases without evidence-backed proof.