Acceptance Criteria

Acceptance Criteria is a Quality skill for Claude Code, published by product-on-purpose in pm-skills.

565 stars74 forkson product-on-purpose/pm-skillsAdded 2026/08/25+3% in starsRepository updated 2026/08/25

agent-skillsagentskillsai-skillsclaude-codeclaude-desktopcodexdesign-sprintfoundation-sprintopenskillsproduct-managementskill-familiestriple-diamond

Install in seconds

Install Acceptance Criteria

Copy Acceptance Criteria into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.

terminal

npx degit https://github.com/product-on-purpose/pm-skills/tree/main/skills/deliver-acceptance-criteria ~/.claude/skills/deliver-acceptance-criteria

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/product-on-purpose/pm-skills.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file: skills/deliver-acceptance-criteria/SKILL.md in product-on-purpose/pm-skills
Installs to: ~/.claude/skills/deliver-acceptance-criteria
Collection: One of 25 skills cataloged from this repository
Category: Quality — 1354 skills

What Acceptance Criteria does

Acceptance Criteria generates testable Given/When/Then scenarios for a user story or feature slice. Use it when turning requirements into engineering handoff and QA sign-off criteria.

Acceptance Criteria is cataloged under Quality on DirSkills. Acceptance Criteria comes from a repository tagged agent-skills, agentskills, ai-skills, claude-code and claude-desktop.

Documentation

README

Excerpt

Acceptance Criteria

Acceptance criteria define the observable behavior that must be true for a story or feature to be considered done. This skill turns feature context into concise, testable Given/When/Then scenarios that engineers and QA can verify without guessing intent.

When to Use

After a user story, PRD section, or feature slice is defined
When a team needs clear pass/fail conditions for implementation
When writing QA-ready criteria for sprint planning or handoff
When a story has edge cases, error paths, or non-functional expectations that should be explicit

This is the opening of the README. Read the full README on GitHub.

Frequently asked about Acceptance Criteria

What else does product-on-purpose publish alongside Acceptance Criteria?
Acceptance Criteria is one of 25 skills that DirSkills catalogs from product-on-purpose/pm-skills, the repository it ships in. Its siblings there include Architecture Decision Record, Build Risk Review and Competitive Analysis. Each one is a separate skill with its own page in this directory, installs the same way Acceptance Criteria does, and is maintained by product-on-purpose in that same repository. The rest of the collection is listed on the product-on-purpose/pm-skills page.
How does Acceptance Criteria compare to other Quality skills?
Acceptance Criteria ranks #1153 by stars among the 1354 Quality skills in this catalog. The most-starred ones next to it are Benchmark, Benchmark Optimization Loop and API Design Patterns. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Acceptance Criteria against them. Open each page to compare what they document and how they install.