User Story Writer
deanpeters/Product-Manager-Skills
Writes user stories in Mike Cohn's format with Gherkin acceptance criteria, turning user needs into development-ready work with testable conditions.
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.
Install Deliver Acceptance Criteria
$ npx skills add product-on-purpose/pm-skills --skill deliver-acceptance-criteria -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install product-on-purpose/pm-skills deliver-acceptance-criteria --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/deliver-acceptance-criteria .claude/skills/deliver-acceptance-criteria && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "deliver-acceptance-criteria" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/deliver-acceptance-criteria into .claude/skills/deliver-acceptance-criteria/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deliver-acceptance-criteria", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/product-on-purpose/pm-skills/tree/main/skills/deliver-acceptance-criteriaType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add product-on-purpose/pm-skills --skill deliver-acceptance-criteria -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install product-on-purpose/pm-skills deliver-acceptance-criteria --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/deliver-acceptance-criteria .agents/skills/deliver-acceptance-criteria && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "deliver-acceptance-criteria" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/deliver-acceptance-criteria into .agents/skills/deliver-acceptance-criteria/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deliver-acceptance-criteria", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add product-on-purpose/pm-skills --skill deliver-acceptance-criteria -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install product-on-purpose/pm-skills deliver-acceptance-criteria --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/deliver-acceptance-criteria .cursor/skills/deliver-acceptance-criteria && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "deliver-acceptance-criteria" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/deliver-acceptance-criteria into .cursor/skills/deliver-acceptance-criteria/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deliver-acceptance-criteria", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/product-on-purpose/pm-skills.git --path skills/deliver-acceptance-criteria--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add product-on-purpose/pm-skills --skill deliver-acceptance-criteria -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install product-on-purpose/pm-skills deliver-acceptance-criteria --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/deliver-acceptance-criteria .gemini/skills/deliver-acceptance-criteria && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "deliver-acceptance-criteria" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/deliver-acceptance-criteria into .gemini/skills/deliver-acceptance-criteria/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deliver-acceptance-criteria", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install product-on-purpose/pm-skills deliver-acceptance-criteriaInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add product-on-purpose/pm-skills --skill deliver-acceptance-criteria -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/deliver-acceptance-criteria .github/skills/deliver-acceptance-criteria && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "deliver-acceptance-criteria" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/deliver-acceptance-criteria into .github/skills/deliver-acceptance-criteria/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deliver-acceptance-criteria", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add product-on-purpose/pm-skills --skill deliver-acceptance-criteria -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install product-on-purpose/pm-skills deliver-acceptance-criteria --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/deliver-acceptance-criteria .opencode/skills/deliver-acceptance-criteria && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "deliver-acceptance-criteria" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/deliver-acceptance-criteria into .opencode/skills/deliver-acceptance-criteria/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deliver-acceptance-criteria", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
deliver-acceptance-criteria- GitHub stars
- 716
- Token cost
- ~1k tokens
- SKILL.md length
- 457 words
- Files
- 6 (incl. references)
- Skills in repo
- 68
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
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.
- Works in 7 steps: Confirm the story or feature scope → Separate the happy path from exceptions → Write each criterion as an observable… → …
- Turning requirements into verifiable scenarios for engineering handoff and QA sign-off
- SKILL.md covers When to Use, When NOT to Use, Instructions and Output Contract, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Deliver Acceptance Criteria is an agent skill from product-on-purpose/pm-skills. 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.
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including reference files (for example `HISTORY.md`, `evals/output-scenarios/bulk-invite.md` and `evals/trigger-fixtures.json`).
It sits in Product & Project Management, covering User stories. The repository describes itself as: 68 plug-and-play, best-practice product management skills for AI agents: 30 Triple Diamond phase + 11 foundation + 12 utility + 15 tool (Foundation Sprint + Design Sprint). Plus… The licence is Apache-2.0.
When your agent uses it
- Turning requirements into verifiable scenarios for engineering handoff and QA sign-off
- Tasks that involve User stories
Example prompts
- “Use the deliver-acceptance-criteria skill to generate structured Given/When/Then acceptance criteria for a user story or feature slice, covering the…”
- “/deliver-acceptance-criteria”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Confirm the story or feature scope
- Separate the happy path from exceptions
- Write each criterion as an observable scenario
- Cover recovery and failure behavior
- Include non-functional expectations
- Avoid duplication and overlap
- Review for testability
What it can do on your machine
Read from SKILL.md and the folder at commit 1cef1a9. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Deliver Acceptance Criteria loads about 1k tokens when it runs, and up to ~2.1k if it reads all its reference files. Until then it costs about 124 tokens; SKILL.md has 457 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from product-on-purpose/pm-skills at commit 1cef1a9, republished under its Apache-2.0 licence (© product-on-purpose). 457 words, ~1,015 tokens.
Download SKILL.mdSave it as
.claude/skills/deliver-acceptance-criteria/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.- name
- deliver-acceptance-criteria
- description
- 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.
- license
- Apache-2.0
- metadata.phase
- deliver
- metadata.version
- 1.1.0
- metadata.updated
- 2026-06-10
- metadata.category
- specification
- metadata.frameworks
- triple-diamond, lean-startup, design-thinking
- metadata.author
- product-on-purpose
<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->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-prdordeliver-user-storiesfirst - You are defining success metrics for an experiment, not done-ness for a story -> use
measure-experiment-design
Instructions
When asked to create acceptance criteria, follow these steps:
Confirm the story or feature scope Identify the exact slice of work. If the scope is unclear, ask for the user story, PRD section, or feature description before drafting criteria.
Separate the happy path from exceptions Start with the primary success flow, then add edge cases and error states that are likely or costly if missed.
Write each criterion as an observable scenario Use Given/When/Then language only. Keep each criterion independently testable and avoid implementation details.
Cover recovery and failure behavior Describe what the user sees or can do when validation fails, a dependency is unavailable, or a save action cannot complete.
Include non-functional expectations Add criteria for performance, accessibility, security, reliability, or auditability when they matter to the story.
Avoid duplication and overlap Each criterion should test one outcome. If two criteria describe the same behavior, merge or split them until the intent is clear.
Review for testability Ensure a reviewer can pass or fail each criterion without interpretation. If a statement is subjective, rewrite it into a measurable outcome.
Show full SKILL.md (116 more words)Show less
Output Contract
Use references/TEMPLATE.md as the output format. A complete response should:
- Restate the feature or story context
- Group criteria into happy path, edge cases, error states, and non-functional criteria
- Use explicit Given/When/Then statements for each criterion
- Note assumptions or open questions when context is incomplete
Quality Checklist
Before finalizing, verify:
- The criteria map to a specific story or feature slice
- The happy path is covered first
- Edge cases are explicit, not implied
- Error states include user-visible recovery behavior
- Non-functional criteria are included when relevant
- Each criterion is testable and has one clear outcome
- No implementation details leak into the acceptance criteria
Examples
See references/EXAMPLE.md for a completed example based on a realistic e-commerce checkout flow.
© product-on-purpose, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 5 other files (references) in skills/deliver-acceptance-criteria of product-on-purpose/pm-skills.
- SKILL.md
- HISTORY.md
- evals/output-scenarios/bulk-invite.md
- evals/trigger-fixtures.json
- references/EXAMPLE.md
- references/TEMPLATE.md
Open the folder on GitHubat commit 1cef1a9
Compare with similar skills
Deliver Acceptance Criteria next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Deliver Acceptance Criteria this skillproduct-on-purpose/pm-skills | 716 | — | ~1k | Automated safety check: Pass | Apache-2.0 | |
| User Story Writerdeanpeters/Product-Manager-Skills | 7.2k | 2 repos | ~2.9k | Automated safety check: Pass | Custom licence | |
| Ralph Tui Create Beadssubsy/ralph-tui | 2.5k | 1 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Agile Product Owneralirezarezvani/claude-skills | 28k | 3 repos | ~3.2k | Automated safety check: Pass | MIT | |
| Ralph Tui Create Beads Rustsubsy/ralph-tui | 2.5k | 1 repos | ~2.8k | Automated safety check: Pass | MIT | |
| To Specbestofjs/bestofjs | 3.1k | 21 repos | ~757 | Automated safety check: Pass | MIT |
Similar skills
Ralph Tui Create Beads
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution. An agent skill from subsy/ralph-tui.
Agile Product Owner
alirezarezvani/claude-skills
Writes INVEST-checked user stories with acceptance criteria, splits epics, plans sprints from velocity and ranks the backlog with a weighted score.
Ralph Tui Create Beads Rust
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution using beads-rust (br CLI).
To Spec
bestofjs/bestofjs
Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
Ralph Tui Create JSON
subsy/ralph-tui
Convert PRDs to prd.json format for ralph-tui execution. An agent skill from subsy/ralph-tui.
More from product-on-purpose/pm-skills
All 68 skills in this repoDefine Hypothesis
product-on-purpose/pm-skills
Defines a testable hypothesis with clear success metrics and a validation approach.
Define Jtbd Canvas
product-on-purpose/pm-skills
Creates a Jobs to be Done canvas capturing the functional, emotional, and social dimensions of a customer job.
Define Opportunity Tree
product-on-purpose/pm-skills
Creates an opportunity solution tree connecting a desired outcome to customer opportunities and candidate solutions, preventing solution-first jumps in continuous discovery.
Define Problem Statement
product-on-purpose/pm-skills
Creates a clear problem framing document with user impact, business context, and success criteria.
Deliver Launch Checklist
product-on-purpose/pm-skills
Creates a cross-functional pre-launch checklist covering engineering, design, marketing, support, legal, and operations readiness, with owners, dates, and go/no-go criteria so nothing is missed…
Deliver Prd
product-on-purpose/pm-skills
Creates a comprehensive Product Requirements Document that aligns stakeholders on what to build, why, and how success will be measured.
Related
Categories
Questions about Deliver Acceptance Criteria
What does Deliver Acceptance Criteria 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. Deliver Acceptance Criteria is an agent skill from product-on-purpose/pm-skills. 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.
When should I use Deliver Acceptance Criteria?
Deliver Acceptance Criteria fits situations like: turning requirements into verifiable scenarios for engineering handoff and QA sign-off; tasks that involve User stories.
How do I install Deliver Acceptance Criteria in Claude Code?
Run `npx skills add product-on-purpose/pm-skills --skill deliver-acceptance-criteria -a claude-code`. Or copy the skill folder (skills/deliver-acceptance-criteria in product-on-purpose/pm-skills) into .claude/skills/deliver-acceptance-criteria in your project. Claude Code loads it when a task matches its description.
How do I install Deliver Acceptance Criteria in Codex?
Run `npx skills add product-on-purpose/pm-skills --skill deliver-acceptance-criteria -a codex`. Or copy the skill folder (skills/deliver-acceptance-criteria in product-on-purpose/pm-skills) into .agents/skills/deliver-acceptance-criteria in your project. Codex loads it when a task matches its description.
Can I use Deliver Acceptance Criteria in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add product-on-purpose/pm-skills --skill deliver-acceptance-criteria -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/deliver-acceptance-criteria, .gemini/skills/deliver-acceptance-criteria, .github/skills/deliver-acceptance-criteria and .opencode/skills/deliver-acceptance-criteria in your project.
What does Deliver Acceptance Criteria need to run?
SKILL.md names no scripts, command-line tools or credentials: Deliver Acceptance Criteria is instructions for the agent only.
Does Deliver Acceptance Criteria access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Deliver Acceptance Criteria safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Deliver Acceptance Criteria use?
Deliver Acceptance Criteria is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Deliver Acceptance Criteria use?
About 1k tokens (SKILL.md is roughly 4.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.1k tokens, read only when the agent opens those files.
What are the alternatives to Deliver Acceptance Criteria?
Skills that share tags, products or a category with Deliver Acceptance Criteria: User Story Writer (deanpeters/Product-Manager-Skills, 7.2k stars), Ralph Tui Create Beads (subsy/ralph-tui, 2.5k stars), Agile Product Owner (alirezarezvani/claude-skills, 28k stars) and Ralph Tui Create Beads Rust (subsy/ralph-tui, 2.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Deliver Acceptance Criteria?
product-on-purpose (a GitHub organization) maintains it in product-on-purpose/pm-skills, which has 716 GitHub stars. The repository holds 68 skills in this directory. The repository was last updated on October 8, 2026.
Source: product-on-purpose/pm-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.