---
name: user-story-mapper
description: "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. 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."
---

# User Story Mapper

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.

## When to use

Use this skill 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 it for writing a single ticket or detailed technical design.

## Workflow

1. Ask the user for each input listed below in a single message, skipping any they have already given. Where options are listed, offer them, but accept other answers too.
2. Lay out the user journey as a backbone of activities in order, based on the primary user's goal.
3. List stories beneath each activity at the chosen granularity, aiming near the requested count.
4. Mark the thinnest slice that delivers value as release one and order the rest by priority.
5. Write each story in the chosen format with acceptance criteria and negative cases if requested.
6. Record dependencies, fit to the framework, and assumptions to confirm.

## Inputs

- **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)

## Output

A journey backbone with stories under each activity in priority order, release-one marked, followed by dependencies and assumptions.

## Prompt template

Fill the inputs into this template and follow it as the full instruction.

### User Story Map

Break the epic below into user stories.

- Epic title: {{Epic title}}
- High-level requirement: {{High-level requirement}}
- Primary user: {{Primary user}}
- The user's main goal: {{The user's main goal}}
- Business rules and background: {{Business rules and background}}
- Technical constraints: {{Technical constraints}}
- Granularity: {{Granularity}}
- Approximate number of stories: {{Approximate number of stories}}
- Include acceptance criteria: {{Include acceptance criteria}}
- Include edge cases and negative scenarios: {{Include edge cases and negative scenarios}}
- Story format: {{Story format}}
- Agile framework: {{Agile framework}}

First lay out the user journey as a backbone of activities from left to right, then list stories beneath each activity in priority order, marking the thinnest slice that delivers value as the first release. Write each story at the chosen granularity and format with criteria and negative cases as requested. Note dependencies between stories and anything that fits the framework, such as sprint-sized splits for Scrum. Finish with assumptions to confirm.

## Pitfalls

- 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.
