abd-story-mapping

Generate Patton-style story maps with epics, sub-epics, and stories.

1|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/agilebydesign/agilebydesign-skills --skill abd-story-mapping
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: abd-story-mapping
Source: https://github.com/agilebydesign/agilebydesign-skills/tree/main/skills/abd-story-mapping
Command: npx skills add https://github.com/agilebydesign/agilebydesign-skills --skill abd-story-mapping

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teaches Patton-style story mapping: epics, sub-epics, stories, verb–noun naming, and actors via story_type. When building a map from sources, outputs all template artifacts in templates/ (currently story-map.md and story-map.txt) with the same tree — not one or the other. Use when structuring product discovery, decomposing user journeys, identifying epics and flows, story mapping, organizing requirements into a hierarchical map, or when the user mentions story maps, epics, sub-epics, or Jeff Patton–style backlog structure.

Core Features & Use Cases

  • Outputs template artifacts in templates/ (story-map.md and story-map.txt) with the same tree structure.
  • Supports mapping from sources (docs, interviews, briefs) into a hierarchical map to identify epics, flows, and narratives.
  • Provides guidance on narrative quality and naming conventions for consistency and reuse.

Quick Start

Create a Patton-style story map from your source materials and produce story-map.md and story-map.txt in templates/.

Frequently Asked Questions about abd-story-mapping

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

FAQPage Schema
How do I create a Patton-style story map from product discovery materials?

Story mapping decomposes user journeys by identifying epics, sub-epics, and stories within source materials. It provides a hierarchical backlog structure that organizes requirements into a narrative flow, helping teams visualize the entire product journey from discovery to implementation.

How do I structure epics and user stories using verb-noun naming conventions?

Verb-noun naming enforces active-language rules for story mapping by pairing an action with an object, such as verb-noun phrasing. This convention keeps epics and stories consistent, clarifies actor intent, and supports reuse across the hierarchical story map.

Can I generate story maps in both markdown and plain text formats?

Yes, story mapping generates complete map pairs in both story-map.md and story-map.txt formats simultaneously. Both artifacts preserve the identical tree structure and connector semantics, ensuring compatibility with the repository's story-map tooling.

What is the best way to organize product requirements into a hierarchical story map?

Organizing requirements into a hierarchical story map involves mapping source materials like interviews and briefs into epics, sub-epics, and stories. This Patton-style approach identifies user flows and narratives, outputting structured templates that preserve the tree structure.

What source materials do I need to build a story map with epics and sub-epics?

Building a story map requires source materials such as product discovery documents, interview notes, or briefs. These inputs are analyzed to identify actors, epics, sub-epics, and stories, which are then organized into a hierarchical map with verb-noun naming.