verify-gate

# verify-gate ## Overview Prove the feature is done. Not guess, not assume — prove. This skill produces a verification report that: (a) lists every spec requirement, (b) names the evidence that each one is satisfied, (c) quotes that evidence verbatim, and (d) reaches a verdict through three independent self-consistency passes. No requirement is marked satisfied without evidence. No evidence is summarized or paraphrased. ## When to invoke - Immediately after `exec-dispatch` reports all tasks complete. - Before `finish-branch`, merge, tag, release, or any outward-facing action. - After a user manually makes changes and asks "is this done?". ## Prerequisites - An approved spec exists at `docs/specs/YYYY-MM-DD-<topic>-design.md` or a path the user specifies. - An approved plan exists at `docs/plans/YYYY-MM-DD-<feature>.md`. - The repo is at the commit the user wants verified. No uncommitted changes unless the user explicitly says otherwise. If any prerequisite fails, stop and surface what is missing. ## Core principle: evidence before assertion Every claim in the verification report takes the form: ``` REQUIREMENT: <quoted from spec, exact> STATUS: satisfied | not satisfied | partial | untestable EVIDENCE: <verbatim quote from test output, git log, file contents, or command output, with the source cited as file:line or command-and-date> ``` If the EVIDENCE field cannot be filled with a real, quotable artifact, STATUS is not `satisfied`. No exceptions for "obvious...