Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add getcrew44/crew44 --skill user-story-mapping-workshopgit clone --depth 1 https://github.com/getcrew44/crew44Wrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/getcrew44/crew44/user-story-mapping-workshop)<a href="https://agentmods.dev/skills/getcrew44/crew44/user-story-mapping-workshop"><img src="https://agentmods.dev/badge/skills/getcrew44/crew44/user-story-mapping-workshop.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00038 | $0.03664 |
| Opus 5 | $0.00019 | $0.01832 |
| Sonnet 5 | $0.00008 | $0.00733 |
| Haiku 4.5 | $0.00004 | $0.00366 |
Grade A, and why
user-story-mapping-workshop scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 478 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
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).
Key Concepts
What is a User Story Map?
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)
Key Principles
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.
Why This Works
- Visual communication: Story maps remain displayed as information radiators, maintaining focus on the big picture
- Narrative structure: Organizes by user workflow, not technical architecture
- Release planning: Horizontal slices reveal MVPs and incremental releases
- Gap identification: Reveals missing functionality that flat backlogs obscure
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 3d ago First seen · 478 lines · 38 tokens per session scan A 317fa65cd230
user-story-mapping-workshop is a skill published in the GitHub repository getcrew44/crew44 (359 stars, last pushed 2mo ago), licensed MIT. It adds 38 tokens to every session and 3,664 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
gitlab
Read and manage GitLab projects, issues, merge requests, and pipelines via the GitLab REST API. Use when the user asks about GitLab projects, issues, MRs, or pipelines.
slack
Read, post, react and search in the connected Slack workspace via the Slack Web API, and help the user finish app setup. Use when the user asks to send a Slack message, list channels or users, read a thread, react to a message, or connect/install the Slack app.
product-strategy
A product-planning guide for evaluating requirements, users, scope, priorities, roadmaps, and success measures. It ties proposals to user problems, business value, boundaries, and signals that can be checked.
github
Read and manage GitHub repos, issues, pull requests, and code search via the GitHub REST API. Use when the user asks about GitHub repos, issues, PRs, or code.
redmine
Read and manage Redmine projects, issues, and updates via the Redmine REST API. Use when the user asks about Redmine tickets/issues or projects.
simply-pm
Use when you are spawned as the PM of a simply harness project and your brief references a .simply/LEDGER.md work ledger or this skill. Grants fleet authority, routing doctrine, safe worker lifecycle, and the signal protocol back to the auditor.