Agent skill

user-story

Create user stories with Mike Cohn format and Gherkin acceptance criteria. Use when turning user needs into development-ready work with clear outcomes and testable conditions.

deanpetersgithub.com/deanpetersGitHub ↗
claude-codeships scriptsNOASSERTION
Install
npx skills add deanpeters/Product-Manager-Skills --skill user-story --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 4
SKILL.md size: 11 KB
Bundled scripts: yes
Path: skills/user-story/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 6,255
Language: Shell
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

## Purpose Create clear, concise user stories that combine Mike Cohn's user story format with Gherkin-style acceptance criteria. Use this to translate user needs into actionable development work that focuses on outcomes, ensures shared understanding between product and engineering, and provides testable success criteria. This is not a feature spec—it's a conversation starter that captures *who* benefits, *what* they're trying to do, *why* it matters, and *how* you'll know it works. ## Input **Works best with:** The feature or user need the story captures. **Also useful:** The user role, the outcome they want, and edge cases the acceptance criteria must cover. Anything supplied with the invocation itself — text after the skill name, a pasted context dump, or an appended `ARGUMENTS:` line — counts as answers already given. Use it and skip whatever it covers; don't re-ask. **Arriving empty-handed? That works too.** The skill asks who the user is and what they're trying to accomplish before drafting story and Gherkin criteria. **Example invocation:** `Write user stories for password reset via SMS for our banking app — include the lockout edge case.` ## Key Concepts ### The Mike Cohn +

What's inside
Steps it walks through
  1. Purpose
  2. Input
  3. Key Concepts
  4. The Mike Cohn + Gherkin Format
  5. Why This Structure Works
  6. Anti-Patterns (What This Is NOT)
  7. When to Use This
  8. When NOT to Use This
  9. Application
  10. Step 1: Gather Context
  11. Optional Helper Script (Template Generator)
  12. Step 2: Write the Use Case
  13. Step 3: Write the Acceptance Criteria
  14. Step 4: Add a Summary
Ships with 3 files
  • examples/sample.md
  • scripts/user-story-template.py
  • template.md
Commands it runs
python3 scripts/user-story-template.py --persona \"trial user\" --action \"log in with Google\" --outcome \"access the app without creating a new password\"
More from Product-Manager-Skills
All skills →
About this skill
What does the user-story skill do?

Create user stories with Mike Cohn format and Gherkin acceptance criteria. Use when turning user needs into development-ready work with clear outcomes and testable conditions.

How do I install it?

Run `npx skills add deanpeters/Product-Manager-Skills --skill user-story --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From deanpeters/Product-Manager-Skills, a repository with 6,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going