
User Story Mapper
Transform customer journeys into sprint-ready user stories with acceptance criteria
What You Can Do
Convert raw customer insights, feature requests, and journey maps into production-ready user stories with measurable acceptance criteria, explicit dependencies, and edge case documentation. Claude structures these stories hierarchically (epic → feature → story), identifies hidden constraints between work items, and generates persona-specific swimlanes that help teams understand the full context before sprint planning.
Features
breaks epics into features into testable user stories with clear relationships
produces measurable, verifiable criteria for each story so QA knows when work is done
surfaces boundary conditions, error states, and assumptions teams might otherwise miss
reveals story sequencing constraints and cross-team blockers before sprint commitment
generates swimlane-oriented stories that show how different user types interact with features
exports structured stories as an interactive board your team can collaborate on synchronously
captures implicit context that keeps engineering from building the wrong thing
Example Output
Input: "Users complain our search is slow and hard to filter by date."
Output:
Epic: Modernize Product Search
Feature: Advanced Search Filters
-
Story 1: As a researcher, I need to filter results by publication date so I find recent sources
- AC: Date picker shows 1-year, 6-month, 1-month presets
- AC: Custom date ranges work across all filter combinations
- Edge case: Handling dates in future (block or warn?)
- Dependency: Search API upgrade (Story 0)
-
Story 2: As a power user, I need to save filter combinations so I don't rebuild searches
- AC: "Save Search" button persists filters to user account
- AC: Saved searches appear in sidebar for 30 days
- Assumption: Users have accounts (may need guest-only flow later)
Swimlane View: Admin users see filter management UI; researchers see simplified filters; power users see advanced + save options.
What's Included
- SKILL.md instruction file: complete prompt for activating the User Story Mapper
- Story mapping template: hierarchical structure (epic → feature → story) with field definitions
- Acceptance criteria checklist: framework for writing testable, measurable criteria
- Dependency graph template: swimlane diagram format for Miro
- Persona narrative guide: how to generate user-type-specific story variations
- Edge case worksheet: systematic approach to identifying boundary conditions and error states
Who It's For
- Product managers — translating roadmaps and customer feedback into actionable sprint work
- Scrum masters/Agile coaches — facilitating story decomposition in team planning sessions
- Engineering leads — getting full context on dependencies and assumptions before estimation
- QA/testing teams — understanding acceptance criteria and edge cases that define test coverage
- UX designers — seeing how different personas interact with features across swimlanes
Best For
- New feature or initiative planning — decomposing strategic goals into testable stories
- Complex, multi-team features — identifying dependencies and sequencing constraints early
- Vague customer requests — turning "make it faster" into measurable acceptance criteria
- Onboarding engineering teams — providing full context and assumptions for a feature area
- Sprint planning preparation — having stories pre-structured so planning sessions stay focused







