/user-story-mapping-workshop

name: user-story-mapping-workshop
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).

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 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