Deliver Acceptance Criteria

Generates structured Given/When/Then acceptance criteria for a user story or feature slice, covering the happy path, key failure scenarios, and non-functional expectations in testable form. Use when turning requirements into verifiable scenarios for engineering handoff and QA sign-off. For a dedicated catalog of boundary conditions, error states, and recovery paths across a feature, use deliver-edge-cases; to write the stories themselves, use deliver-user-stories.

819 stars 104 forksWriting & Content Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add product-on-purpose/pm-skills

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 product-on-purpose/pm-skills --skill deliver-acceptance-criteria
Manual install
git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git /tmp/pm-skills
mkdir -p ~/.claude/skills
cp -r /tmp/pm-skills/skills/deliver-acceptance-criteria ~/.claude/skills/deliver-acceptance-criteria

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

## When NOT to Use

- You need the user stories themselves -> use `deliver-user-stories`; this skill deepens a story that already exists
- You need systematic failure coverage across a whole feature -> use `deliver-edge-cases`; this skill stays story-scoped
- There is no story or slice to bind criteria to yet -> use `deliver-prd` or `deliver-user-stories` first
- You are defining success metrics for an experiment, not done-ness for a story -> use `measure-experiment-design`
- The criterion is a rate over model output, such as "90% of answers are faithful to their sources" -> use the AI Behavior and Evaluation section of `deliver-prd`, which says a rate needs a designed sample to verify it, and what to record until one exists

## Instructions

When asked to create acceptance criteria, follow these steps:

1. **Confirm the story or feature scope**
Read the full skill on GitHub

Details

Skill name
deliver-acceptance-criteria
Path
skills/deliver-acceptance-criteria/SKILL.md
License
Apache-2.0
Repo updated
17 November 2026

FAQ

What does the Deliver Acceptance Criteria skill do?

Generates structured Given/When/Then acceptance criteria for a user story or feature slice, covering the happy path, key failure scenarios, and non-functional expectations in testable form. Use when turning requirements into verifiable scenarios for engineering handoff and QA sign-off. For a dedicated catalog of boundary conditions, error states, and recovery paths across a feature, use deliver-edge-cases; to write the stories themselves, use deliver-user-stories.

How do I install the Deliver Acceptance Criteria skill?

Claude Code plugin: /plugin marketplace add product-on-purpose/pm-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Deliver Acceptance Criteria popular?

It lives in product-on-purpose/pm-skills, which has 819 GitHub stars and 104 forks, and is included in 2 curated skill lists.

Related skills

<phase or Classification Skill Name>

819

product-on-purpose/pm-skills

<single-line 20-100 word description; include trigger keywords and do not use folded YAML>

Skill & Plugin AuthoringIn 2 lists104

Define Hypothesis

819

product-on-purpose/pm-skills

Defines a testable hypothesis with clear success metrics and a validation approach. Use when forming assumptions to test or aligning a team on what success looks like, before any experiment is designed. To design the A/B test or experiment that will validate the hypothesis, use measure-experiment-design.

Finance & CryptoIn 2 lists104

Define Jtbd Canvas

819

product-on-purpose/pm-skills

Creates a Jobs to be Done canvas capturing the functional, emotional, and social dimensions of a customer job. Use when deeply understanding customer motivations, designing for jobs, or reframing product positioning.

Frontend & DesignIn 2 lists104

Deliver User Stories

819

product-on-purpose/pm-skills

Generates user stories in the standard persona, action, benefit story format from product requirements or feature descriptions. Use when breaking a feature into stories for sprint planning, writing tickets, or communicating scope to engineering. For testable Given/When/Then acceptance criteria on a story, use deliver-acceptance-criteria; for boundary and failure scenarios, use deliver-edge-cases.

Writing & ContentIn 2 lists104

Visual Content Desc

2.1k

aipoch/medical-research-skills

Generates detailed text descriptions of medical images and charts for.

Writing & Content206

Foundation Build Risk Review

819

product-on-purpose/pm-skills

Runs a fast pre-build risk review on a product idea, feature request, or scope change, naming the single assumption most likely to make it fail and returning a clear verdict (build small, validate first, pivot first, or don't build yet) with a no-code validation step. Use before committing build effort, when triaging whether to honor a feature request, or when deciding whether to expand scope, ahead of writing a PRD. For a launched product's pivot-or-persevere decision, use iterate-pivot-decision instead.

Writing & ContentIn 2 lists104

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