
User Story Writer
Turns a feature idea into structured user stories with acceptance criteria
- Repository
- phuryn/pm-skills
- Stars
- 27,616
- Licence
- MIT
- Files
- 1 file
What it does
Once installed, the agent breaks a product feature into backlog-ready user stories, each written as a short title, a plain-language 'As a [user], I want [action], so that [benefit]' description, a design link placeholder, and 4-6 testable acceptance criteria. It follows the 3 C's (Card, Conversation, Confirmation) and INVEST criteria (Independent, Negotiable, Valuable, Estimable, Small, Testable). It is guided by a template and an example, and it is told to use plain language.
Great for
- Product managers writing backlog items for a sprint
- Agile teams who want consistent story format and acceptance criteria
- Students or new team members learning how user stories are structured
Skip it if
- Teams needing a verified requirements document: the output is generated text and must be reviewed against real user research and product decisions
- Non-software work where user stories do not apply, since the template is built around product features
Try asking
- “Break this checkout redesign into user stories with acceptance criteria: [paste feature description and Figma link]”
- “Write user stories for a 'Recently viewed' section on our product page”
- “Turn these meeting notes on password reset into INVEST-compliant backlog items”
Install in 3 steps
- 1
Download the skill
The ZIP contains the 1 original files, the MIT licence and an attribution note.
user-stories.zip - 2
Add it to your agent
Claude Code (all projects)
mkdir -p ~/.claude/skills && unzip user-stories.zip -d ~/.claude/skills/Claude Code / Agent SDK (this project only)
mkdir -p .claude/skills && unzip user-stories.zip -d .claude/skills/Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.
- 3
Ask for the task
No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.
Get better results
- Provide the product name, the feature, a design link and key assumptions so the stories reflect real context rather than guesses.
- Review the generated acceptance criteria against your actual requirements, since the example and template may introduce details you did not intend.
- Ask for stories to be split further if any one is too large to finish in a single sprint.
What's inside
- SKILL.md
Redistributed unmodified from phuryn/pm-skills under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.