ac-checker


Type	Skill
Plugin	awl-general · v0.0.51
Invoke	`/awl-general:ac-checker`
Tools	Read, Write, Edit, Bash, Glob, Grep, Task
Source	plugins/awl-general/skills/ac-checker/SKILL.md

When Claude uses it

Verify acceptance criteria implementation status from Jira, ClickUp, GitLab, or GitHub issues. Triggers: “check ACs”, “verify story”, “validate acceptance criteria”, “check issue implementation”. Auto-extracts issue from branch name.

Trigger phrases: check ACs · verify story · validate acceptance criteria · check issue implementation

Definition

Validates that acceptance criteria from issue trackers are implemented and tested in the codebase.

Instructions

Step 1: Get Issue Number

git branch --show-current

Extract from branch patterns:

Pattern	Example	Issue
Jira	`feature/IES-12345-desc`	`IES-12345`
GitLab/GitHub	`feature/123-desc`	`123`
ClickUp	`feature/abc123-desc`	`abc123`

If not found, ask: “What issue number should I check?”

Step 2: Detect & Fetch Issue

Check available MCP tools:

Tracker	MCP Prefix	Fetch Command
Jira	`mcp__atlassian__`	`getJiraIssue(cloudId, issueIdOrKey)`
ClickUp	`mcp__clickup__`	`clickup_get_task(task_id)`
GitLab	`mcp__gitlab__` or CLI	`glab issue view <num>`
GitHub	`mcp__github__` or CLI	`gh issue view <num>`
Linear	`mcp__linear__`	Use Linear MCP tools

If no MCP: “Please paste the acceptance criteria or provide a URL.”

Step 3: Extract ACs

Parse from description field. Look for:

“Acceptance Criteria”, “Akzeptanzkriterien”, “AC:”
Numbered lists (1., 2., AC1:)
Checkbox items (- [ ])

Step 4: Verify (Parallel Agents)

Launch TWO parallel Task agents:

Agent 1 - Implementation Check:

Check if these ACs are implemented:
[List ACs]
Search: domain models, ViewModels, UI, APIs
Return: AC#: [found/not found] - [file:line] - [notes]

Agent 2 - Test Coverage Check:

Check test coverage for these ACs:
[List ACs]
Search: *Test.kt, *Tests.swift, *.test.ts, *.spec.ts
Return: AC#: [tested/not tested] - [test file:line]

Step 5: Generate Report

## AC Status Report: [ISSUE-NUMBER]
**Issue**: [Title] | **Branch**: [branch]

### Status
| AC | Description | Implementation | Tests |
|----|-------------|----------------|-------|
| 1 | [summary] | ✅ file.kt:123 | ✅ FileTest.kt:45 |
| 2 | [summary] | ✅ file.kt:200 | ❌ MISSING |
| 3 | [summary] | ❌ NOT FOUND | ➖ |

### Summary
- ✅ Implemented + Tested: X
- ⚠️ Missing Tests: X
- ❌ Not Implemented: X
- 🔍 Manual Check Needed: X

### Recommendations
[Specific actions to complete the story]

Troubleshooting

Issue	Solution
No issue in branch	Ask user for issue number
No MCP available	Ask user to paste ACs directly
Can’t find implementation	Check shared/, platform-specific, and common/ folders
ACs too vague	Report as “Manual Check Needed”

Examples

Jira: “check ACs” on branch feature/IES-16564-journal

Extracts IES-16564, fetches via Atlassian MCP, reports status

GitLab: “verify issue 42”

Runs glab issue view 42, parses ACs, searches codebase

ClickUp: “check task abc123”

Uses clickup_get_task, extracts ACs from description