Agent skill · Workflow & Productivity

user-story-mapping

Create a user story map that lays out activities, steps, tasks, and release slices. Use when planning a workflow, backlog, or MVP around the user journey.

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

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

Facts
Files in the skill folder: 3
SKILL.md size: 11 KB
Bundled scripts: none
Path: skills/user-story-mapping/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 Visualize the user journey by creating a hierarchical map that breaks down high-level activities into steps and tasks, organized left-to-right as a narrative flow. Use this to build shared understanding across product, design, and engineering, prioritize features based on user workflows, and identify gaps or opportunities in the user experience. This is not a backlog—it's a strategic artifact that shows *how* users accomplish their goals, which then informs *what* to build. ## Input **Works best with:** The product or user workflow being mapped. **Also useful:** The primary user, the end-to-end narrative as you understand it, existing backlog items to place, and release goals. 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 whose journey you're mapping and what they're trying to get done, then builds backbone → tasks → slices. **Example invocation:** `Story map for our expense-reporting flow, from receipt capture to reimbursement, with an MVP slice f

What's inside
Steps it walks through
  1. Purpose
  2. Input
  3. Key Concepts
  4. The Jeff Patton Story Mapping Framework
  5. Story Map Structure
  6. Why This Works
  7. Anti-Patterns (What This Is NOT)
  8. When to Use This
  9. When NOT to Use This
  10. Application
  11. Step 1: Define the Context
  12. Step 2: Define the Narrative
  13. Step 3: Identify Activities (Backbone)
  14. Step 4: Break Activities into Steps
Ships with 2 files
  • examples/sample.md
  • template.md
More from Product-Manager-Skills
All skills →
About this skill
What does the user-story-mapping skill do?

Create a user story map that lays out activities, steps, tasks, and release slices. Use when planning a workflow, backlog, or MVP around the user journey.

How do I install it?

Run `npx skills add deanpeters/Product-Manager-Skills --skill user-story-mapping --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