Agent skill · Workflow & Productivity

user-story-mapping-workshop

Run a user story mapping workshop with adaptive questions and a structured map output. Use when you need backbone activities, tasks, and release slices for a workflow.

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

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

Facts
Files in the skill folder: 2
SKILL.md size: 16 KB
Bundled scripts: none
Path: skills/user-story-mapping-workshop/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 Guide product managers through creating a user story map by asking adaptive questions about the system, users, workflow, and priorities—then generating a two-dimensional map with backbone (activities), user tasks, and release slices. Use this to move from flat backlogs to visual story maps that communicate the big picture, identify missing functionality, and enable meaningful release planning—avoiding "context-free mulch" where stories lose connection to the overall system narrative. This is not a backlog generator—it's a visual communication framework that organizes work by user workflow (horizontal) and priority (vertical). ## Input **Works best with:** The system or workflow to map. **Also useful:** The primary users, workflow steps you already know, and what the map must decide (MVP scope, release plan). 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 workshop opens by asking about the system and its users (Q1), then proceeds per the facilitation protocol.

What's inside
Steps it walks through
  1. Purpose
  2. Input
  3. Key Concepts
  4. What is a User Story Map?
  5. Key Principles
  6. Why This Works
  7. Anti-Patterns (What This Is NOT)
  8. When to Use This
  9. When NOT to Use This
  10. Facilitation Source of Truth
  11. Application
  12. Step 0: Gather Context (Before Questions)
  13. Question 1: Define Scope
  14. Question 2: Identify Users/Personas
Ships with 1 file
  • template.md
More from Product-Manager-Skills
All skills →
About this skill
What does the user-story-mapping-workshop skill do?

Run a user story mapping workshop with adaptive questions and a structured map output. Use when you need backbone activities, tasks, and release slices for a workflow.

How do I install it?

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