acceptance-criteria-verification

Verifies GitHub issue acceptance criteria with structured tests and posts verification reports.

Updated Jan 1, 2026
One-click install
npx skills add https://github.com/sarkarshivaditya-lab/WellMate --skill acceptance-criteria-verification-sarkarshivaditya-lab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: acceptance-criteria-verification
Source: https://github.com/sarkarshivaditya-lab/WellMate/tree/main/.engineering-skills/troykelly-claude-skills/skills/acceptance-criteria-verification
Command: npx skills add https://github.com/sarkarshivaditya-lab/WellMate --skill acceptance-criteria-verification-sarkarshivaditya-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After implementing a feature, teams often lack a systematic way to confirm every acceptance criterion in a GitHub issue actually works, leading to untested requirements and undocumented verification. ## Core Features & Use Cases - Criterion Extraction and Planning: Parses acceptance criteria from GitHub issue bodies and maps each one to a unit, integration, E2E, or manual test approach. - Structured Verification Reports: Posts a formatted report to the issue with PASS/FAIL/PARTIAL/SKIP statuses, evidence, test output, and next steps. - Issue and Project Sync: Checks off passing criteria in the issue body and updates project fields like verification status and criteria met count. - Use Case: After finishing a feature branch, run this Skill against issue #42 to execute the relevant tests, capture evidence, and post a complete verification report as an issue comment. ## Quick Start Verify all acceptance criteria in GitHub issue 42 against the current implementation and post the verification report.

Frequently Asked Questions about acceptance-criteria-verification

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify acceptance criteria in a GitHub issue?

Extract the criteria from the issue body using gh issue view, map each criterion to a unit, integration, E2E, or manual test, execute the verification, and post a structured report with PASS, FAIL, PARTIAL, or SKIP statuses as an issue comment.

How to run E2E verification for acceptance criteria?

Run Playwright tests with npx playwright test or use browser automation MCP tools. Start a fresh browser session, capture screenshots at key points, check visible rendered state, and clean up sessions after verification.

What statuses are used in acceptance criteria verification reports?

Each criterion receives PASS (fully met), FAIL (not met, needs fix), PARTIAL (works with issues), or SKIP (blocked or not applicable). The report summarizes counts per status and lists next steps for failures.

Can verification results update GitHub project fields automatically?

Yes. After verification, the workflow updates project fields such as verification status (Passing, Failing, or Partial), criteria met count, last verified date, and verified-by, using the project-status-sync skill.

What should I do when an acceptance criterion fails verification?

Document specifically what failed, include reproduction steps and error messages or screenshots, return to development to fix the issue, and re-run verification. Never mark a failed criterion as PASS or skip verification.