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/.