usm-expert

Review User Story Mapping artifacts for narrative flow and release slicing.

2|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/boykush/livt --skill usm-expert
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: usm-expert
Source: https://github.com/boykush/livt/tree/main/plugins/discovery-facilitator/skills/usm-expert
Command: npx skills add https://github.com/boykush/livt --skill usm-expert

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides expert consultation and review for User Story Mapping, grounded in Jeff Patton's methodology, to enhance narrative flow, structure, and release slicing.

Core Features & Use Cases

  • Expertise in User Story Mapping: Grounded in Jeff Patton's work, offering narrative flow, backbone structure, release slicing, and story scope analysis.
  • Review and Consultation: Assist in reviewing story maps, answering USM questions, and challenging scope for structural critique.
  • Consulting Guidelines: Follows established principles and anti-patterns to ensure the integrity of User Story Mapping artifacts.

Quick Start

Request an expert review of your User Story Map by typing 'usm-expert review my-map'.

Frequently Asked Questions about usm-expert

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

FAQPage Schema
How do I review my User Story Mapping artifacts for structural integrity?

To review User Story Mapping artifacts, this consultation analyzes narrative flow, backbone structure, user tasks, and release slices against Jeff Patton's methodology to identify anti-patterns and ensure structural integrity.

What are common User Story Mapping anti-patterns to avoid when structuring a backbone?

Common User Story Mapping anti-patterns include misaligned backbone structure, disjointed narrative flow, and improper release slicing, which violate Jeff Patton's methodology and disrupt the user's journey mapping.

How do I slice release versions effectively using Jeff Patton's user story mapping methodology?

Slicing release versions effectively using Jeff Patton's user story mapping requires organizing user tasks horizontally by narrative flow and vertically by priority, ensuring each release slice delivers end-to-end value.

Do I need prior knowledge of Jeff Patton's principles to get a user story mapping consultation?

Yes, you need a foundational understanding of User Story Mapping principles and anti-patterns, as this consultation provides expert review of your artifacts rather than teaching the basics of Jeff Patton's methodology.

Can I use this consultation to challenge the scope of user tasks in my story map?

Yes, you can use this consultation to challenge story scope, as it provides structural critique and guidance on your user tasks to ensure they align properly within the overall user story mapping backbone.

Why does my user story map lack narrative flow when organizing user tasks?

Your user story map may lack narrative flow if the backbone structure and user tasks deviate from Jeff Patton's methodology, requiring a structural critique to realign the release slices and story scope.