story-mapping

Builds Jeff Patton user story maps with backbones, walking skeletons, and release slices.

3|2|Updated Aug 24, 2026
One-click install
npx skills add https://github.com/hero-engine/hero --skill story-mapping-hero-engine
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: story-mapping
Source: https://github.com/hero-engine/hero/tree/main/domains/pm/skills/story-mapping
Command: npx skills add https://github.com/hero-engine/hero --skill story-mapping-hero-engine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Flat backlogs hide whether the work adds up to a usable product, and teams often polish one feature corner while the core user journey remains incomplete. This Skill turns a one-dimensional backlog into a two-dimensional story map so gaps, priorities, and minimum viable releases become visible. ## Core Features & Use Cases - Backbone Construction: Arranges user activities left to right in narrative order, with tasks ranked vertically by priority beneath each activity. - Walking Skeleton Slicing: Identifies the thinnest end-to-end path across all activities so release 1 delivers a complete, if crude, user journey. - Release Planning: Cuts horizontal slices across the map so every release spans the whole journey instead of completing one activity at a time. - Use Case: A team planning an expense-reporting tool maps Capture receipt through Reimburse, then ships a thin skeleton (photo upload, category list, one-click approve) before adding OCR and approval routing in release 2. ## Quick Start Use the story-mapping skill to break this initiative into a story map with a walking skeleton and three release slices.

Frequently Asked Questions about story-mapping

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a user story map for a new feature?▼

Frame one user and one goal, lay the backbone of user activities left to right in narrative order, then fill tasks downward under each activity. Rank each column vertically by essentiality and cut a horizontal line below the top task in every column to define the walking skeleton release.

What is a walking skeleton in story mapping?▼

A walking skeleton is the thinnest path across the entire backbone: the minimum task under each activity so a real user completes the full journey end to end. It works end to end but has no depth, and you build it before adding enhancements in later releases.

How does story mapping differ from a flat prioritized backlog?▼

A flat backlog answers what is next but cannot show whether the pieces form a usable journey. The story map adds a horizontal narrative dimension, making gaps visible, such as ranking attachments above send, which a list would hide until build time.

When should I not use story mapping?▼

Avoid mapping features or components instead of user activities, slicing releases by technical layer like backend then frontend, and piling every enhancement into release 1. If no user performs a backbone step, it does not belong on the map.

How do story map items become development stories?▼

Map cells are candidate stories, not finished ones. Each task committed to a release is authored as an INVEST story with its own acceptance criteria; the map provides the slicing while INVEST provides the story shape.