Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →nwave-ai/nw-user-story-mapping
User story mapping for backlog management and outcome-based prioritization. Load during Phase 2.5 (User Story Mapping) to produce story-map.md and prioritization.md.
Passed 20 of 22 test cases with the skill, and 10 of 22 without it.
and 12 more in the full report
11 fixed9 passed either way1 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are evaluating a story map release for a mobile banking app. On a 1-5 scale, outcome value is rated 4, time urgency is rated 5, and effort complexity is rated 2. Calculate the Priority Score using the standard user story mapping prioritization formula.
| Checked | Without skill | With skill |
|---|---|---|
| Output calculates the Priority Score as 10. | Missed | Passed |
The instructions your model reads when the skill loads.
Create story maps that organize user stories spatially by activity and priority, then slice releases by outcome impact. Reference: Jeff Patton, "User Story Mapping" (2014). Integrates outcome-based prioritization from Gothelf/Seiden and riskiest-assumption-first from Maurya.
| Element | Position | Purpose |
|---|---|---|
| Backbone | Top row, left-to-right | User activities in chronological order -- the spine of the journey |
| Ribs | Columns under each activity | User tasks broken down vertically by detail and priority |
| Walking Skeleton | Horizontal line across all activities | Thinnest possible end-to-end working flow. Not an MVP -- it is the minimum slice that connects ALL activities |
| Release Slices | Horizontal bands below skeleton | Coherent groups of stories, each adding incremental value tied to a specific outcome |
Visual structure:
Activity A Activity B Activity C Activity D
----------- ----------- ----------- -----------
Task A.1 Task B.1 Task C.1 Task D.1 <- Walking Skeleton
........... ........... ........... ........... <- skeleton line
Task A.2 Task B.2 Task C.2 Task D.2 <- Release 1
Task A.3 Task B.3 <- Release 1
Task B.4 Task C.3 Task D.3 <- Release 2
Identify the user persona and their end-to-end goal. One map per persona-goal pair.
Write the big activities left-to-right in chronological order. These are verb phrases: "Search products", "Compare options", "Complete purchase". Aim for 4-8 activities.
Under each activity, list the tasks that support it. Write as short action phrases (user behaviors). Place more detail and less critical tasks lower.
Reorder tasks within each column: most critical at top, nice-to-have at bottom. Ask: "Which task is essential for this activity to work at all?"
test cases passed, vs 10 / 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.