| name | ac-verify |
| description | Verifies each AC against implementation in a single pass before Archive. TRIGGER: Phase 5 QA with AC ≤ 3 AND risk ≠ HIGH. NOT FOR: AC ≥ 4 or HIGH risk (use ultraqa); writing tests (use lead-engineer). |
Verify
What This Does
Use this skill to turn “it should work” into concrete, observable evidence.
When to Use
- User asks to verify correctness (e.g., “verify”, “make sure it works”)
- After implementing a feature, bugfix, or refactor
- Before declaring completion or handing off work
Protocol
- Identify the exact behavior(s) that must be proven
- Prefer existing tests and existing gates
- If coverage is missing, run the narrowest direct verification available
- If automation is insufficient, provide a minimal manual verification procedure and capture observable evidence
- Report only what was actually verified
Verification Order (Preferred)
- Existing tests
- Typecheck / build (if applicable)
- Narrow, direct command checks
- Manual or interactive verification (last resort)
Rules
- Do not claim completion without evidence
- If verification fails, include the failure signal and what remains unverified
- If no realistic verification path exists, say so explicitly
- Prefer concise evidence summaries over noisy logs
Output Format
- What was verified
- Commands/tests executed
- What passed
- What failed or remains unverified
Related Skills
- ultraqa: Use when you need a bounded “fail → diagnose → fix → re-verify” loop
- root-cause-debug: Use when verification fails and you must find root cause before fixing
- code-review-checklist: Run before delivery for self-review gates
