From silver-bullet
Verifies completed work against plan, spec, tests, UAT criteria. Checks acceptance criteria, runs tests, records evidence, blocks shipping on unresolved BLOCK findings.
How this skill is triggered — by the user, by Claude, or both
Slash command
/silver-bullet:silver-verify <phase or completion claim><phase or completion claim>The summary Claude sees in its skill listing — used to decide when to auto-load this skill
SB-owned verification checks actual artifacts, acceptance criteria, tests, and
SB-owned verification checks actual artifacts, acceptance criteria, tests, and evidence rather than agent confidence.
Write or update .planning/phases/<phase>/VERIFICATION.md or
.planning/VERIFICATION.md for project-level work.
SILVER BULLET > VERIFY.verify-tests when the verification requires a
broader test gate.silver:domain-audit with test-health plus the affected
domain packs. Verification may reuse an existing fresh DOMAIN-AUDIT.md only
when it covers the current diff and command evidence.silver:test instead of
accepting coverage as a vague follow-up. Use the relevant mode:
write, e2e, repair, audit, performance, or mutation.silver-bullet.md §8.1
fallback hierarchy:
do / check / get for
acceptance-criteria evidence; attach results to VERIFICATION.md.browser_click / browser_type / browser_scroll,
verify state via browser_snapshot, and capture browser_take_screenshot
per criterion. Cursor: cursor-ide-browser tools. Attach evidence to
VERIFICATION.md.silver:add.Verification passes only when:
npx claudepluginhub alo-exp/silver-bullet --plugin silver-bulletGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.