verification-looplisted

# Verification Loop Skill > Derived from the `verification-loop` skill in everything-claude-code (ECC), used under the MIT > License. A comprehensive verification system for coding sessions. The job is not "run the gates" — it is to **verify the changed behavior through the surface a real user or consumer actually uses**, and to end with one verdict that cannot be softened into prose. ## When to Use Invoke this skill: - After completing a feature or significant code change - Before creating a PR - When you want to ensure quality gates pass - After refactoring - To verify that a fix actually closed the reported failure ### Positive triggers - "Verify this implementation before handoff." - "Confirm the bug is closed in the real CLI." - "Run visual and functional QA on the changed flow." ### Negative triggers - Pure planning with no artifact to verify. - A generic request for more tests with no changed behavior or acceptance criterion in hand. - Anything where you would be verifying code you just wrote yourself (see the Verdict Contract). ## Pick the real surface first Static gates support verification; they do not constitute it. Before running anything, list the acceptance criteria as observable outcomes and select every track the change touches — UI, API/service, CLI/TUI, library/SDK, documents/configuration, user flow. Each track has a required observation and its own evidence record: read [references/tracks.md](references/tracks.md). ## Then pick the depth — it sc