01 Acceptance QA

Validate a reviewed candidate's observable behavior against its acceptance criteria and record short named videos as reviewer evidence. Use when acceptance criteria exist and a browser-observable journey needs proof it holds. Do NOT use for diff review, unit or integration tests, or application fixes.

564 stars 65 forksTesting & QA Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add ai-driven-dev/framework

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add ai-driven-dev/framework --skill 01-acceptance-qa
Manual install
git clone --depth 1 https://github.com/ai-driven-dev/framework.git /tmp/framework
mkdir -p ~/.claude/skills
cp -r /tmp/framework/plugins/aidd-qa/skills/01-acceptance-qa ~/.claude/skills/01-acceptance-qa

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Acceptance QA

```mermaid
flowchart LR
  scope["load-scope"] --> prerequisites["prerequisites"] --> prepare["prepare-run"] --> run["run-scenarios"] --> report["qa.md"]
  scope -- skipped --> report
```

## Actions

Read only the next action's file before running it.

| #   | Action          | Does                                                       |
| --- | --------------- | ---------------------------------------------------------- |
| 01  | `load-scope`    | Lock at most one happy path and the edge cases its acceptance criteria name |
| 02  | `prerequisites` | Verify the browser runner and media dependencies            |
| 03  | `prepare-run`   | Resolve the shortest deterministic path to executable runs |
| 04  | `run-scenarios` | Record, normalize, verify, reset, and report every scenario |

## Transversal rules

- Run against a reviewed change and never patch the application.
- Never delete data not proven test-only.
- Never derive a scenario from the diff or the source code; every scenario traces to an acceptance criterion.
- Never spawn agents. Batch independent reads and tool checks, but keep state-changing browser work sequential.
- Do not narrate action transitions, searches, fixtures, selectors, or successful checks. Report only a blocker, a required decision, or the final verdict and paths.
Read the full skill on GitHub

Details

Skill name
01-acceptance-qa
Path
plugins/aidd-qa/skills/01-acceptance-qa/SKILL.md
License
MIT
Repo updated
18 November 2026

FAQ

What does the 01 Acceptance QA skill do?

Validate a reviewed candidate's observable behavior against its acceptance criteria and record short named videos as reviewer evidence. Use when acceptance criteria exist and a browser-observable journey needs proof it holds. Do NOT use for diff review, unit or integration tests, or application fixes.

How do I install the 01 Acceptance QA skill?

Claude Code plugin: /plugin marketplace add ai-driven-dev/framework. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is 01 Acceptance QA popular?

It lives in ai-driven-dev/framework, which has 564 GitHub stars and 65 forks.

Related skills

00 Async Dev

564

ai-driven-dev/framework

Drive the async-dev pipeline from one entry point, whether setup, run, or review. Use when the user wants to install async dev, run a ready issue, or address PR review comments, or on a webhook trigger. Not for plain status checks.

Git & Code Review65

00 Init

564

ai-driven-dev/framework

Turn AIDD measurement on for a project after explicit consent, stop it, choose to be named on your own measurement, or delete what was measured. Use when the user wants to start or stop measuring what their work consumes, add or remove their name, or forget measured data. Not for answering what a period consumed.

Other65

00 Onboard

564

ai-driven-dev/framework

Guide a project's journey through AIDD, from first setup to shipping a feature. Use when the user says onboard me, where do I start, or what to do next. Not for listing every installed surface.

Other65

06 Test

564

ai-driven-dev/framework

Write and iterate developer-side tests until they pass, or validate a user journey end to end in the browser during implementation. Use when the user wants to add coverage, find what's untested, or walk a flow while building it. Do NOT use for independent acceptance QA or reviewer evidence, auditing test health, or debugging a failure.

Testing & QA65

Mean Reversion

564

agiprolabs/claude-trading-skills

Mean-reversion strategy tools including Hurst exponent, half-life estimation, z-score signals, ADF testing, and Ornstein-Uhlenbeck modeling

Testing & QA113

Character Sim

593

haowjy/creative-writing-skills

Load to speak as a specified character from what they know, how they talk, and what they feel now: in-character conversation, voice discovery, or a relationship pressure test. Pass the character, the story moment, and their style and character-state files.

Testing & QA82

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.