skill-verification-before-completion

Run focused proof first: the original reproduction or regression test, tests nearest the changed behavior, and affected validators or builds. Then reconcile every plan task and acceptance criterion against fresh evidence before setting the plan status to completed.

Valid evidence is fresh output from named commands or direct inspection that proves each specific claim, such as a passing test run or a clean validator exit. Old output, plan checkboxes, code review, and agent summaries do not qualify as completion proof.

No. Verification only makes Git closure eligible and explicitly prohibits commits, rebases, merges, pushes, pull requests, and worktree removal. Branch disposition is handed off to a separate finishing skill after a verified result.

The failure is reported with the exact command, relevant output, and a classification of introduced, pre-existing, environmental, external, or unknown. Introduced or unknown failures return to implementation and debugging skills, and the plan status stays non-completed.

Evidence can be reused only within the active operation when command identity, changed files, environment, worktree identity, and ownership inputs remain valid. Any content-changing commit, rebase, or generated refresh invalidates the affected evidence.