User Story Mapping
Apply Jeff Patton's User Story Mapping (O'Reilly, 2014) — arranging user stories into a two-dimensional map that preserves the user's narrative journey, which a flat backlog destroys. Covers the map's anatomy (backbone and ribs; activities, tasks, details), the two axes (narrative flow left-to-right, priority/necessity top-to-bottom), the core philosophy (shared understanding over documents; minimize output, maximize outcome and impact), running a mapping workshop (frame, map breadth-first, explore alternatives/exceptions, distill a backbone, slice), slicing releases into a walking-skeleton MV
Install
/plugin marketplace add vnovakovits/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add vnovakovits/claude-skills --skill user-story-mappinggit clone --depth 1 https://github.com/vnovakovits/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/plugins/engineering-practices/skills/user-story-mapping ~/.claude/skills/user-story-mappingPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# User Story Mapping (Jeff Patton) Apply this skill when planning a product, a release, or a sizeable feature; when a flat backlog has turned into a pile of disconnected stories nobody can see the shape of; when you need to carve a genuine MVP that still tells a complete story end-to-end; when running a discovery or release-planning workshop; or whenever you want to reason about work by the **user's journey and the outcome you're after** rather than a feature checklist. A story map is a simple idea: lay the user's story out left-to-right in the order it happens, break each step down top-to-bottom, and you get a two-dimensional picture that a one-dimensional backlog throws away. The map is a tool for *building shared understanding*, not a document to hand off. ## Core Philosophy **The goal is shared understanding, not documents.** Patton's central claim: *"Shared documents are not shared understanding."* Good design documents are *"like vacation photos"* — they help the people who were in the room relive and recall the conversation, but they fail to give the same information to anyone who wasn't there. The book's section titles say it plainly: *"Building Shared Understanding Is Disruptively Simple,"* *"Stop Trying to Write Perfect Documents,"* *"Good Documents Are Like Vacation Photos."* Kent Beck's line, quoted in the book, is the slogan: *"Stop exchanging documents. Tell me your story."* (Patton is **not** anti-document — he advocates
Details
- Skill name
user-story-mapping- Repository
- vnovakovits/claude-skills
- Path
plugins/engineering-practices/skills/user-story-mapping/SKILL.md- License
- MIT
- Repo updated
- 16 November 2026
FAQ
What does the User Story Mapping skill do?
Apply Jeff Patton's User Story Mapping (O'Reilly, 2014) — arranging user stories into a two-dimensional map that preserves the user's narrative journey, which a flat backlog destroys. Covers the map's anatomy (backbone and ribs; activities, tasks, details), the two axes (narrative flow left-to-right, priority/necessity top-to-bottom), the core philosophy (shared understanding over documents; minimize output, maximize outcome and impact), running a mapping workshop (frame, map breadth-first, explore alternatives/exceptions, distill a backbone, slice), slicing releases into a walking-skeleton MV
How do I install the User Story Mapping skill?
Claude Code plugin: /plugin marketplace add vnovakovits/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is User Story Mapping popular?
It lives in vnovakovits/claude-skills, which has 5 GitHub stars and 2 forks.
Related skills
Accidental Cio
5vnovakovits/claude-skills
Apply Scott Millett's "The Accidental CIO — A Lean and Agile Playbook for IT Leaders" (Wiley, 2024) when designing or reviewing how a technology organisation decides, funds, governs and delivers work. Covers the five components of an adaptive IT operating model (organised, work, govern, talent, lead) and its four themes (outcomes over output, intrinsic motivation, being not doing agile, manage flow not people); matching method and governance to context via Cynefin and Wardley evolution; governance as demand management + funding + measurement + decision rights, shifting from project funding to
Agent Retro
5vnovakovits/claude-skills
Run a retrospective on a coding-agent session and improve the agent's environment, not the code. Combines Derby & Larsen's five-stage retrospective, Shigeo Shingo's poka-yoke (turn a mechanical mistake into a check that makes it impossible), and Matt Pocock's retro categories — navigation, automated checks, coding standards, steering files, tool economy, information access. Covers mining the session transcript for corrections, wrong turns and slow searches; deciding where each fix belongs (analyzer, hook, CI, reviewer standards, CLAUDE.md pointer, skill, doc or memory); the no-op test for stee
API Design
5vnovakovits/claude-skills
Design APIs that are clear, evolvable, and idiomatic to their protocol — covering REST (Fielding, Richardson Maturity Model, Massé), GraphQL, gRPC/protobuf, versioning strategies, pagination, error responses (RFC 7807 Problem Details), idempotency, authentication, documentation (OpenAPI), and the pragmatic trade-offs between RESTful purity and developer ergonomics. Use when designing a new endpoint, choosing between REST/GraphQL/gRPC, defining versioning, structuring error responses, deciding pagination strategy, or evaluating an existing API's evolvability.
Validate Docs Implementation
8Freddy-CHEN-ux/00_claude_skills
Load when user says "validate docs", "check documentation consistency", "docs vs implementation", or "find documentation mismatches". Systematically compares implementation code against documentation to identify and fix inconsistencies.
Update Workspace Map
8Freddy-CHEN-ux/00_claude_skills
Validate workspace-map.md accuracy against actual 04-workspace/ structure (3 levels deep). Load when user says "validate workspace map", "update workspace map", "check workspace map", or from close-session. Ensures deep structure validation with comprehensive documentation.
Value Stream Mapping
5vnovakovits/claude-skills
Map how a request flows from ask to value — Mike Rother & John Shook's "Learning to See" (1999) and Karen Martin & Mike Osterling's "Value Stream Mapping" (2013), adapted to software and knowledge work. Covers scoping one value stream, the map grammar (process boxes with lead time, process time and %C&A, queue triangles, push and pull arrows, information flow, the timeline ladder, kaizen bursts), collecting real numbers from tracker state history instead of opinions, the summary metrics (total lead time, process time, flow efficiency or activity ratio, rolled %C&A), the future-state questions,
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.