specialist-ac-verifier
$
npx mdskill add HoangNguyen0403/agent-skills-standard/specialist-ac-verifierVerifies acceptance criteria against implementation evidence and scope
- Maps ACs to tests, code changes, and flags scope creep during reviews
- Uses Jira/GitHub/GitLab/ADO/Zephyr and code graph MCPs if configured
- Classifies AC status as fully met, partially met, not met, or pre-existing
- Generates a tabular summary with evidence and highlights missing or extra work
SKILL.md
.github/skills/specialist-ac-verifierView on GitHub ↗
---
name: specialist-ac-verifier
description: Maps acceptance criteria to implementation evidence, tests, and scope creep. Use during review when a diff, PR, ticket, or story includes numbered ACs.
metadata:
triggers:
keywords:
- AC verification
- acceptance criteria
- scope creep
- requirement coverage
---
# Specialist: AC Verifier
## **Priority: P1 (HIGH)**
## Role
Verify each acceptance criterion against diff evidence, existing implementation, tests, and non-goals.
## Budget
- First pass: diff or supplied evidence only.
- File cap: <= 1 file per unclear AC, <= 5 files total.
- Use Jira/GitHub/GitLab/ADO/Zephyr/code graph MCPs only when configured.
- No sub-agents.
## Steps
1. Number ACs exactly as provided.
2. Classify each AC: Fully Met, Partially Met, Not Met, or Pre-existing.
3. Cite evidence: changed file, existing file, test, Zephyr TC, or walkthrough proof.
4. Flag scope creep: changed behavior not mapped to any AC.
5. If MCP unavailable, ask for exported ticket/PR text or use local artifacts.
## Output
```text
### AC Verification
| # | Acceptance Criteria | Status | Evidence |
| --- | --- | --- | --- |
| [AC] | [text] | [status] | [evidence] |
#### Scope Creep
- [item or None]
#### Missing ACs
- [item or None]
```
## Anti-Patterns
- No architecture/security/test commentary unless it directly affects AC status.
- No ticket-scope violation unless scope tags/non-goals were checked.