facilitate-user-story-mapping

Guide users through creating User Story Maps via structured phases.

1|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/EnigmaWU/MyCodeAgentSkills --skill facilitate-user-story-mapping
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: facilitate-user-story-mapping
Source: https://github.com/EnigmaWU/MyCodeAgentSkills/tree/main/facilitate-user-story-mapping
Command: npx skills add https://github.com/EnigmaWU/MyCodeAgentSkills --skill facilitate-user-story-mapping

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the creation of User Story Maps, enhancing shared understanding and preventing the development of unsuitable products.

Core Features & Use Cases

  • Structured User Story Mapping: Guided through Jeff Patton's process for building a 2D matrix of product requirements.
  • End-to-End Narrative Flow: Focuses on end-to-end narratives and functional walking skeletons to ensure viable product releases.
  • Use Case: When a team is about to develop a new feature, use this Skill to create a User Story Map, ensuring every step of the product lifecycle is considered.

Quick Start

Trigger the skill by stating "Let's break down this feature" and the skill will guide you through the User Story Mapping process.

Frequently Asked Questions about facilitate-user-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 agile product development?

Creating a user story map involves executing Context Gathering, Backbone Creation, Task Fleshing, and Slice Definition phases to build a 2D matrix of product requirements for structured agile planning.

What is user story mapping and when do I need it for requirement analysis?

User story mapping is a structured requirement analysis technique that arranges product features into an end-to-end narrative flow. You need it to ensure shared understanding and prevent developing unsuitable products.

How do I break down a new feature into an end-to-end narrative flow?

To break down a feature, provide clear user personas and feature descriptions to trigger the mapping process. The Skill will structure these inputs into a functional walking skeleton for viable product releases.

Does user story mapping require predefined user personas and feature descriptions?

Yes, user story mapping requires clear user input for feature descriptions and user personas. Providing these predefined inputs is essential to accurately execute the Context Gathering and Backbone Creation phases.

What is the best way to define viable product releases using structured requirement analysis?

The best way to define viable product releases is through Slice Definition, which identifies functional walking skeletons within your user story map to ensure your product lifecycle steps are fully considered and release-ready.