User Story Mapping Workshop
Facilitate a Jeff Patton–style story mapping session that outputs backbone activities, user tasks, and vertical release slices instead of a flat backlog.
Overview
User Story Mapping Workshop is an agent skill most often used in Validate scope (also Build pm) that runs an adaptive workshop and outputs backbone activities, tasks, and release slices.
Install
npx skills add https://github.com/deanpeters/product-manager-skills --skill user-story-mapping-workshopWhat is this skill?
- Interactive workshop with adaptive questions on system, users, workflow, and priorities
- Two-dimensional map: horizontal user workflow backbone (activities + tasks) and vertical priority/release slices
- Explicitly avoids “context-free mulch” backlogs disconnected from the system narrative
- Organizes work for meaningful release planning—not an automatic story generator
- Structured output aligned to Jeff Patton user story mapping concepts
- Two-dimensional map structure: horizontal workflow backbone and vertical release slices
Adoption & trust: 1.2k installs on skills.sh; 5k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your backlog is a flat list of stories that no longer shows the full user workflow or what belongs in the next release.
Who is it for?
Product-minded solo builders scoping an MVP or major workflow who need release slices tied to a coherent user journey.
Skip if: Teams that already maintain an approved story map, or pure engineering tasks with no user-journey narrative (e.g., dependency bumps only).
When should I use this skill?
You need backbone activities, user tasks, and release slices for a workflow—not a flat backlog dump.
What do I get? / Deliverables
You get a visual story map with backbone activities, granular user tasks, and prioritized release slices ready to inform roadmap and build planning.
- User story map with backbone activities and tasks
- Prioritized release slices across the workflow
- Workshop captures from system, user, and priority Q&A
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Validate → scope because the skill turns workflow understanding into prioritized release slices before full build commitment. Subphase scope captures user journeys, MVP boundaries, and release planning—not post-launch analytics or infra operations.
Where it fits
Map primary user activities to see which jobs your MVP must serve before you write marketing copy.
Define horizontal workflow steps and vertical release slices to decide what ships in v1 versus v2.
Refresh the map after technical discovery so sprint goals still match the narrative backbone.
Communicate upcoming release themes using slice names tied to user activities stakeholders already recognize.
How it compares
A facilitated story-mapping workshop skill—not a Jira CSV exporter or generic user-story generator.
Common Questions / FAQ
Who is user-story-mapping-workshop for?
Solo founders and indie PMs using Claude Code or Cursor who need Jeff Patton–style maps to communicate scope and releases without a facilitation coach in the room.
When should I use user-story-mapping-workshop?
Use it in Validate scope when defining MVP slices from a workflow, in Build pm when re-planning after discovery, and in Idea audience work when you need to align jobs-to-be-done to a visual journey—before you commit sprint backlog items.
Is user-story-mapping-workshop safe to install?
It is conversational planning content; avoid sharing sensitive customer data in workshop answers. Review the Security Audits panel on this page before install.
SKILL.md
READMESKILL.md - User Story Mapping Workshop
## 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). ## Key Concepts ### What is a User Story Map? A story map (Jeff Patton) organizes user stories in **two dimensions**: **Horizontal axis (left to right):** Activities arranged in narrative/workflow order—the sequence you'd use explaining the system to someone **Vertical axis (top to bottom):** Priority within each activity, with the most essential tasks at the top **Structure:** ``` Backbone (Activities across top) ↓ User Tasks (descending vertically by priority) ↓ Details/Acceptance Criteria (at the bottom) ``` ### Key Principles **The Backbone:** Essential activities form the system's structural core—these aren't prioritized against each other; they're the narrative flow. **Walking Skeleton:** The highest-priority tasks across all activities form the minimal viable product—the smallest end-to-end functionality. **Ribs:** Supporting tasks descend vertically under each activity, indicating priority through placement. **Left-to-Right, Top-to-Bottom Build Strategy:** Build incrementally across all major features rather than completing one feature fully before starting another. ### Why This Works - **Visual communication:** Story maps remain displayed as information radiators, maintaining focus on the big picture - **Narrative structure:** Organizes by user workflow, not technical architecture - **Release planning:** Horizontal slices reveal MVPs and incremental releases - **Gap identification:** Reveals missing functionality that flat backlogs obscure ### Anti-Patterns (What This Is NOT) - **Not a Gantt chart:** Story maps show priority, not time estimates - **Not technical architecture:** Maps follow user workflow, not system layers (UI → API → DB) - **Not a project plan:** It's a discovery and communication tool, not a schedule ### When to Use This - Starting a new product or major feature - Reframing an existing backlog (moving from flat list to visual map) - Aligning stakeholders on scope and priorities - Planning MVP or incremental releases ### When NOT to Use This - Single-feature projects (story map overkill) - When backlog is already well-understood and prioritized - For technical refactoring work (no user workflow to map) --- ### Facilitation Source of Truth Use [`workshop-facilitation`](../workshop-facilitation/SKILL.md) as the default interaction protocol for this skill. It defines: - session heads-up + entry mode (Guided, Context dump, Best guess) - one-question turns with plain-language prompts - progress labels (for example, Context Qx/8 and Scoring Qx/5) - interruption handling and pause/resume behavior - numbered recommendations at