User Story Mapper skill for Claude and Codex
Breaks an epic or high-level requirement into a set of ordered user stories, with acceptance criteria and negative cases, sized for your agile team.
Install it once and Claude or Codex runs it for you. When your request matches, your AI loads the skill, asks for anything it is missing, and works through the template itself. Prefer to fill it in by hand? See the full prompt template.
Download the skill (.zip) · View SKILL.md
When it is used
Use when a team has an epic or broad requirement and needs it mapped into a prioritised set of stories across the user journey. Do not use for writing a single ticket or detailed technical design. Related topics: product, ux, agile.
What it will ask you for
- Epic title (free text, e.g. "Online course enrolment system")
- High-level requirement (longer free text)
- Primary user (free text, e.g. "Student or administrator or teacher")
- The user's main goal (free text, e.g. "The outcome they want")
- Business rules and background (longer free text)
- Technical constraints (longer free text)
- Granularity (choose one: Epics or features, User stories, Small dev-ready stories)
- Approximate number of stories (number from 1 to 25)
- Include acceptance criteria (choose one: Yes, No)
- Include edge cases and negative scenarios (choose one: Yes, No)
- Story format (choose one: As a role I want a goal so that a benefit, Given When Then, Bulleted list)
- Agile framework (choose one: Scrum, Kanban, SAFe, Other)
How it works
- Lay out the user journey as a backbone of activities in order, based on the primary user's goal.
- List stories beneath each activity at the chosen granularity, aiming near the requested count.
- Mark the thinnest slice that delivers value as release one and order the rest by priority.
- Write each story in the chosen format with acceptance criteria and negative cases if requested.
- Record dependencies, fit to the framework, and assumptions to confirm.
What you get
A journey backbone with stories under each activity in priority order, release-one marked, followed by dependencies and assumptions.
What it watches out for
- Slicing by technical layer, which produces stories no user would notice.
- Listing stories with no order, so the first release is never defined.
- Copying the same acceptance criteria across stories instead of tailoring them.
How to install
Claude.ai and the Claude desktop app
- Download the skill .zip.
- Open Settings, then Capabilities, and find Skills.
- Choose Upload skill and select the .zip.
- Ask Claude for help with the task. It loads the skill when your request matches.
Claude Code
- Download the skill .zip.
- Unzip it into ~/.claude/skills/ (or .claude/skills/ inside a project).
- Start a new session. Claude Code loads the skill when your request matches.
Codex
- Download the skill .zip.
- Unzip it into ~/.agents/skills/ (or .agents/skills/ inside a project).
- Codex picks it up on its own. Type $ and the skill name to use it, or just ask for the task.
Cursor
- Download the Cursor rule (.mdc).
- Save it in .cursor/rules/ inside your project.
- Cursor's agent applies the rule when your request matches its description.
AGENTS.md (Codex, Cursor, and other coding agents)
- Copy the AGENTS.md section.
- Paste it into AGENTS.md at the root of your repository, creating the file if needed.
- Coding agents that read AGENTS.md follow it when your request fits.