Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →getcrew44/user-story-mapping-workshop
Run a user story mapping workshop with adaptive questions and a structured map output.
Passed 20 of 22 test cases with the skill, and 16 of 22 without it.
and 1 more in the full report
4 fixed16 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
I want to run a workshop session to map out our new telemedicine patient app. I have a flat list of ideas, but I need help building a two-dimensional user story map step-by-step. Please ask me questions one at a time to establish the scope, primary personas, the high-level activity backbone, user tasks under each activity, and finally slice them into incremental releases starting with a minimal walking skeleton. Walk me through this standard workshop flow.
| Checked | Without skill | With skill |
|---|---|---|
| Prompts for initial context or scope definition using enumerated options. | Missed | Passed |
| Limits the turn to a single prompt. | Passed | Passed |
The instructions your model reads when the skill loads.
Guide product managers through creating a user story map by asking adaptive questions about the system, users, workflow, and priorities—then generating a two-dimensional map with backbone (activities), user tasks, and release slices. Use this to move from flat backlogs to visual story maps that communicate the big picture, identify missing functionality, and enable meaningful release planning—avoiding "context-free mulch" where stories lose connection to the overall system narrative.
This is not a backlog generator—it's a visual communication framework that organizes work by user workflow (horizontal) and priority (vertical).
A story map (Jeff Patton) organizes user stories in two dimensions:
Horizontal axis (left to right): Activities arranged in narrative/workflow order—the sequence you'd use explaining the system to someone
Vertical axis (top to bottom): Priority within each activity, with the most essential tasks at the top
Structure:
Backbone (Activities across top)
↓
User Tasks (descending vertically by priority)
↓
Details/Acceptance Criteria (at the bottom)
The Backbone: Essential activities form the system's structural core—these aren't prioritized against each other; they're the narrative flow.
Walking Skeleton: The highest-priority tasks across all activities form the minimal viable product—the smallest end-to-end functionality.
Ribs: Supporting tasks descend vertically under each activity, indicating priority through placement.
Left-to-Right, Top-to-Bottom Build Strategy: Build incrementally across all major features rather than completing one feature fully before starting another.
test cases passed, vs 16 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.