deliver-user-stories
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.
npx skills add product-on-purpose/pm-skills --skill deliver-user-stories --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 --> # User Stories User stories are concise descriptions of functionality from the user's perspective. They capture who needs something, what they need, and why - without prescribing how to build it. Good user stories enable teams to break large features into estimable, deliverable increments while maintaining focus on user value. ## When to Use - After PRD approval, when breaking down features for implementation - During sprint planning to create actionable work items - When writing tickets for engineering teams - When communicating requirements to stakeholders in accessible terms - When prioritizing a backlog based on user value ## When NOT to Use - You need deeper, QA-ready Given/When/Then coverage for a single story or slice -> use `deliver-acceptance-criteria` - You need the feature-wide catalog of boundary conditions and failure scenarios -> use `deliver-edge-cases` - The feature itself is not yet specified -> use `deliver-prd` first; stories should trace back to documented requirements - You want refinement-session outcomes (estimates, scope decisions, open questions) -> use `iterate-refinement-not
- When to Use
- When NOT to Use
- Instructions
- Output Format
- Quality Checklist
- Examples
What does the deliver-user-stories skill do?
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.
How do I install it?
Run `npx skills add product-on-purpose/pm-skills --skill deliver-user-stories --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 product-on-purpose/pm-skills, a repository with 518 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.