# Deliver User Stories

Generates user stories in the standard persona, action, benefit story format from...

- Repository: https://github.com/product-on-purpose/pm-skills (780 stars)
- Category: Writing
- License: Apache-2.0
- Last updated: 2026-10-31
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add product-on-purpose/pm-skills --skill deliver-user-stories -g -a claude-code -y`
Codex: `npx skills add product-on-purpose/pm-skills --skill deliver-user-stories -g -a codex -y`
Cursor: `npx skills add product-on-purpose/pm-skills --skill deliver-user-stories -g -a cursor -y`
Gemini CLI: `npx skills add product-on-purpose/pm-skills --skill deliver-user-stories -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add product-on-purpose/pm-skills`

## Description

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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

<!-- 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-notes`

## Instructions

When asked to create user stories, follow these steps:

1. **Understand the Feature Context**
   Review the PRD or feature description. Understand the overall goal, target users, and scope boundaries. User stories should trace back to documented requirements.

2. **Identify User Personas**
   Determine which users interact with this feature. Each story should be written for a specific persona, not generic "users." Different personas may need different stories for the same feature.

3. **Break Down by User Goal**
   Decompose the feature into distinct user goals. Each story should deliver a complete, valuable capability - something the user can actually do when the story is done.

The rest: https://github.com/product-on-purpose/pm-skills/blob/HEAD/skills/deliver-user-stories/SKILL.md