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.
Installs just this skill. Get the whole plugin for auto-invocation.
⚡ How it fires
How this skill gets triggered: by you, by Claude, or both.
Fires itselfClaude auto-loads it when your prompt matches the work.
You can call itInvoke it directly when you want it.
Slash command/user-story-mapping-workshop
👁️ Context preview
The summary Claude sees to decide when to auto-load this skill.
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.
---name: user-story-mapping-workshop
argument-hint: "[system or workflow]"
description: 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.
intent: >-
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.
type: interactive
---## 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.
**Example invocation:** `Run a story mapping workshop for our vendor onboarding portal — output should give us a first release slice.`
## 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.
- progress labels (for example, Context Qx/8 and Scoring Qx/5)
- interruption handling and pause/resume behavior
- numbered recommendations at decision points
- quick-select numbered response options for regular questions (include `Other (specify)` when useful)
This file defines the domain-specific assessment content. If there is a conflict, follow this file's domain logic.
## Application
This interactive skill asks **up to 5 adaptive questions**, offering **3-4 enumerated options** at each step.
Use `template.md` for the facilitation agenda and outputs checklist.
Interaction pattern: Pair with `skills/workshop-facilitation/SKILL.md` when you want a one-step-at-a-time flow with numbered recommendations at decision points and quick-select options for regular questions. If the user asks for a single-shot output, skip the multi-turn facilitation.
---
### Step 0: Gather Context (Before Questions)
**Agent suggests:**
Before we create your story map, let's gather context:
**Product/Feature Context:**
- What system or feature are you mapping?
- Product concept, PRD draft, or existing backlog
- Website copy, positioning materials, or user flows
- Existing user stories (if transitioning from flat backlog)
**User Context:**
- Target personas or user segments
- User research, interviews, or journey maps
- Jobs-to-be-done or problem statements
**You can paste this content directly, or describe the system briefly.**
---
### Question 1: Define Scope
**Agent asks:**
"What are you mapping? (What's the scope?)"
**Offer 4 enumerated options:**
1. **Entire product** — "Full end-to-end system from discovery to completion" (Common for new products or full rewrites)
2. **Major feature area** — "Specific workflow within a larger product (e.g., 'onboarding,' 'checkout,' 'reporting')" (Common for feature launches)
3. **User journey** — "Specific user goal or job-to-be-done (e.g., 'hire a contractor,' 'file taxes')" (Common for JTBD-driven mapping)
4. **Redesign/refactor** — "Existing product/feature being rebuilt or simplified" (Common for legacy system modernization)
**Or describe your specific scope.**
**User response:** [Selection or custom]
---
### Question 2: Identify Users/Personas
**Agent asks:**
"Who are the primary users for this map? (List personas or user segments.)"
**Offer 4 enumerated options:**
1. **Single persona** — "One primary user type (e.g., 'small business owner')" (Simplifies mapping, good for MVP)
2. **Multiple personas, shared workflow** — "Different user types, same core activities (e.g., 'buyer' and 'seller' both browse listings)" (Common for marketplaces)
3. **Multiple personas, different workflows** — "Different user types with distinct workflows (e.g., 'admin' vs. 'end user')" (Requires separate maps or swim lanes)
4. **Roles within organization** — "Different job functions (e.g., 'PM,' 'designer,' 'engineer')" (Common for internal tools)
**Or describe your users.**
**Adaptation:** Use personas from context provided in Step 0 (proto-personas, JTBD, etc.)
**User response:** [Selection or custom]
---
### Question 3: Generate Backbone (Activities)
**Agent says:**
"Let's build the backbone—the narrative flow of activities users perform to accomplish their goal."
**Agent generates 5-8 activities** based on scope (Q1) and users (Q2), arranged left-to-right in workflow order.
**Example (if Scope = "E-commerce checkout"):**
```
Backbone Activities (left to right):
1. Browse Products
2. Add to Cart
3. Review Cart
4. Enter Shipping Info
5. Enter Payment Info
6. Confirm Order
7. Receive Confirmation
```
**Agent asks:**
"Does this backbone capture the full workflow? Should we add, remove, or reorder activities?"
**User response:** [Approve, modify, or add custom activities]
---
### Question 4: Generate User Tasks (Under Each Activity)
**Agent says:**
"Now let's add user tasks under each activity, organized by priority (top = must-have, bottom = nice-to-have)."
**Agent generates 3-5 user tasks per activity**, arranged vertically by priority.
**Example (for Activity 2: "Add to Cart"):**
```
Add to Cart (Activity)
├─ Add single item to cart (must-have, walking skeleton)
├─ Adjust quantity (must-have)
├─ Add multiple items at once (should-have)
├─ Save item for later (nice-to-have)
└─ Add gift wrapping (nice-to-have)
```
**Agent repeats for all backbone activities**, showing the full map.
**Agent asks:**
"Does this capture the key tasks? Are priorities correct (top = MVP, bottom = later releases)?"
**User response:** [Approve, modify, or add custom tasks]
