Skip to content
Back to skills

Specialist Ac Verifier

ASecurity

Maps acceptance criteria to implementation evidence, tests, and scope creep. Use during review when a diff, PR, ticket, or story includes numbered ACs.

  • 549 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added June 6, 2026
developmentgogitsecurity

Works with

  • mcp

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned October 3, 2026

npx -y skills add HoangNguyen0403/agent-skills-standard --skill specialist-ac-verifier --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Specialist Ac Verifier?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Specialist Ac Verifier
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/hoangnguyen0403-specialist-ac-verifier/badge)](https://www.skillsdirectory.com/skills/hoangnguyen0403-specialist-ac-verifier)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
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:
  internal: true
  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.
- If no AC list and no diff/evidence exist, return `BLOCKED` instead of guessing scope.

## 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.

Files in this skill

  • SKILL.md1.4 KB
  • evals/evals.json604 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.