Turns a feature idea into clear user stories with acceptance criteria your team can build and test.
WHEN TO USE IT
When a feature idea needs to become work items a team can pick up.
Formats change. If a field stops working, check it against Anthropic's documentation.
One file. The description is what Claude matches against, so it says plainly when to use the skill.
---
name: user-stories
description: Turn a feature idea into user stories with acceptance criteria. Use when the user asks for user stories, backlog items, tickets or acceptance criteria.
---
Write user stories for a feature.
1. If the feature, the type of user or the problem it solves is missing, ask once, in one message, then continue.
2. Split the feature into small stories, each one deliverable on its own.
3. Write each story as: As a [type of user], I want [goal], so that [benefit].
4. Under each story, give three to five acceptance criteria in the form: Given [context], when [action], then [result].
5. Add a short "Out of scope" list so the edges are clear.
6. Finish with a table: story, priority (must, should, could), open questions.
Rules:
- Do not invent business rules, numbers or limits; write [check] where the team must decide.
- Keep each story about user value, not about how it is built.
- Flag any story that looks too large to finish in one sprint.Put the folder in your skills directory. Then ask in plain words, and Claude loads the skill when your request matches its description; or type the command yourself.
# for you, in every project
mkdir -p ~/.claude/skills/user-stories
mv SKILL.md ~/.claude/skills/user-stories/
# then, inside Claude Code, either ask naturally:
# write user stories for a password reset feature
# or run it by name:
# /user-storiesMORE SKILLS
The authority
Anthropic's documentation for Skills
This template is a starting point. Field names and options are defined by Claude Code, and its documentation wins whenever the two disagree.
https://code.claude.com/docs/en/skills