agentleFS
nisarthnisarth/claude-skills-store/skills/product-management/user-story-mapping/SKILL.md

user-story-mapping

Skill1 starsChanged 7 months agoMITView on GitHub

Map user stories to identify personas, journey steps, activities, and prioritize releases. Use when planning a new product or feature area, breaking a large initiative into shippable slices, aligning the team on what to build first, or visualizing the user journey to find gaps. Trigger phrases: "user story map", "story mapping", "map the user journey", "break this down into stories", "plan the releases", "journey mapping", "what should we ship first", "slice this feature", "user flow breakdown"

11 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use derisk-measurement-advisor, organic-growth-advisor and 5 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • DIAL-StudioSkill

    derisk-measurement-advisor

    Identify what to measure, test, or track to de-risk a product or AI idea. Use when stress-testing an idea across internal (DUFV) and external (PESTEL) dimensions.

    Also in 3 projects that use this

  • DIAL-StudioSkill

    organic-growth-advisor

    Identify which organic growth path to pursue — new segments, geographies, channels, or products. Use when diagnosing where a growth constraint lives and which McKinsey growth level to act\

    Also in 3 projects that use this

  • ian-lawrence423Skill

    skill-authoring-workflow

    Create or update repo skills with compliant metadata, dependency contracts, package sync, marketplace descriptions, and validation workflow.

    Also in 3 projects that use this

  • skytiger6724Skill

    lean-canvas

    Generate a Lean Canvas with problem, solution, metrics, cost structure, UVP, unfair advantage, channels, segments, and revenue. Use when exploring a lean startup canvas, testing a business hypothesis, or modeling a new venture.

    Also in 4 projects that use this

  • AnasX7Skill

    minimalist-ui

    Clean editorial-style interfaces. Warm monochrome palette, typographic contrast, flat bento grids, muted pastels. No gradients, no heavy shadows.

    Also in 3 projects that use this

  • AnasX7Skill

    design-taste-frontend

    Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create user story maps that visualize the user journey, organize stories by activity, and slice releases into shippable increments.

    line 12
  2. Distinctive:

    If multiple personas use the same flow, note where their journeys diverge.

    line 28
  3. Distinctive:

    Read left to right as a story: "First the user does X, then Y, then Z"

    line 41
  4. Distinctive:

    Use 5-8 activities. Fewer is too vague.

    line 42
  5. Distinctive:

    Release 1: should be a "walking skeleton" -- thin end-to-end slice that covers the whole journey, even if minimally.

    line 96
  6. Distinctive:

    Prefer wide and thin (one task per activity) over narrow and deep (all tasks in one activity).

    line 98
  7. Distinctive:

    Response: Start with the primary persona (project manager).

    line 153

“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

User Story Mapping

Create user story maps that visualize the user journey, organize stories by activity, and slice releases into shippable increments. Based on Jeff Patton's story mapping methodology.

Workflow

Step 1: Identify the Persona

Define who you are mapping for:

### Persona: [Name/Role]
**Who**: [Description -- role, context, technical level]
**Goal**: [What they are ultimately trying to accomplish]
**Current pain**: [What frustrates them today]
**Frequency**: [How often they do this activity]

If multiple personas use the same flow, note where their journeys diverge.

Step 2: Map the Backbone

The backbone is the top-level narrative flow -- the big activities the user performs in order:

[Activity 1] --> [Activity 2] --> [Activity 3] --> [Activity 4] --> [Activity 5]

Activities are high-level verbs: "Discover," "Evaluate," "Purchase," "Onboard," "Configure," "Use Daily," "Get Help."

Guidelines:

  • Read left to right as a story: "First the user does X, then Y, then Z"
  • Use 5-8 activities. Fewer is too vague; more is too granular.
  • Each activity should take minutes to hours, not seconds or days.

Step 3: Add User Tasks

Under each activity, list the specific tasks the user performs:

Activity: Onboard
  |
  +-- Create account
  +-- Verify email
  +-- Complete profile
  +-- Connect integrations
  +-- Invite team members
  +-- Take guided tour

Order tasks within each activity from most essential (top) to least essential (bottom). This vertical ordering drives release planning.

Step 4: Build the Full Map

## Story Map: [Feature/Product Name]
Persona: [Name]

| Discover | Evaluate | Sign Up | Onboard | Use Core | Get Help |
|----------|----------|---------|---------|----------|----------|
| Search | View pricing | Create acct | Profile | [Task] | FAQ |
| Browse | Compare | Verify | Integrations | [Task] | Chat |
| Referral | Free trial | | Team invite | [Task] | Ticket |
| Ad click | Demo | | Tour | [Task] | Docs |

Each column is an activity. Each row represents decreasing priority within that activity.

Step 5: Slice into Releases

Draw horizontal lines across the map to define releases:

--- Release 1 (MVP): Walking Skeleton ---
| Search | View pricing | Create acct | Profile | [Core task] | FAQ |

--- Release 2: Viable Product ---
| Browse | Compare | Verify | Integrations | [Task 2] | Chat |
| Referral | Free trial | | Team invite | [Task 3] | |

--- Release 3: Complete Experience ---
| Ad click | Demo | | Tour | [Task 4] | Ticket |
| | | | | [Task 5] | Docs |

Release slicing principles:

  • Release 1 should be a "walking skeleton" -- thin end-to-end slice that covers the whole journey, even if minimally.
  • Each release should be independently shippable and deliver user value.
  • Prefer wide and thin (one task per activity) over narrow and deep (all tasks in one activity).

Step 6: Define Stories for the Current Release

For each task in the target release, write user stories:

### [Activity] > [Task]

**Story**: As a [persona], I want to [task] so that [benefit].

**Acceptance criteria**:
- [Criterion 1]
- [Criterion 2]

**Size**: [S/M/L]
**Dependencies**: [Other stories]
**Notes**: [Design considerations, technical notes]

Step 7: Compile the Story Map Document

## User Story Map: [Product/Feature]
Date: [Date] | Persona: [Name]

### Persona
[Persona card]

### Journey Backbone
[Activity flow]

### Full Story Map
[Map table]

### Release Plan
- **Release 1**: [Name/theme] | [N stories] | [Target date]
  [Stories list]
- **Release 2**: [Name/theme] | [N stories] | [Target date]
  [Stories list]

### Gaps Identified
- [Missing activity or task discovered during mapping]

### Assumptions
- [Assumption about user behavior to validate]

### Open Questions
- [Question requiring research or decision]

Examples

Example 1: New Product

User: "Map user stories for our new project management tool." Response: Start with the primary persona (project manager). Map the backbone: Create Project, Add Tasks, Assign Team, Track Progress, Report Status. Add tasks under each. Slice Release 1 as the minimal viable workflow: create project, add tasks, mark complete.

Example 2: Feature Area

User: "Break down our billing and payments feature into releases." Response: Map the backbone: View Plan, Upgrade, Enter Payment, Manage Billing, View Invoices. Slice Release 1: view current plan, upgrade with card payment, view invoices. Release 2: downgrade, payment methods, billing contacts. Release 3: usage-based billing, multi-currency.

Example 3: Improving Existing Flow

User: "Our onboarding has too many steps. Help me figure out what to cut." Response: Map the current onboarding flow. Identify which tasks are essential for activation vs. nice-to-have. Move non-essential tasks below the Release 1 line or defer them to post-onboarding. Validate by checking: can a user get value with only the Release 1 tasks?

Best Practices

  1. Map with the team. Story mapping works best as a collaborative exercise. The map is a communication tool, not just a planning artifact.
  2. Walk the skeleton. Release 1 should cover the entire journey thinly. Users need to complete the full flow, even if each step is minimal.
  3. Prioritize vertically. Within each activity column, the most important task should be at the top. This makes release slicing visual and intuitive.
  4. Challenge every task. For each task, ask: "What happens if we skip this?" If the answer is "nothing breaks," it might not be Release 1.
  5. One persona at a time. Map the primary persona first. Then overlay secondary personas and note where journeys diverge.
  6. Stories, not features. Each item on the map should describe something a user does, not something the system has. "User filters results" not "Filter component."
  7. Validate with real users. The map represents your assumption of the user journey. Test it by observing real users or walking through it with them.
  8. Revisit after each release. The map should evolve as you learn. What you assumed was Release 2 priority may change based on Release 1 feedback.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.