Agent skill

user-story-writer

Write well-structured user stories with acceptance criteria and edge cases. Use when asked to write user stories, create tickets from a feature brief, convert a PRD into stories, or write acceptance criteria. Produces ready-to-estimate stories in the standard format with clear acceptance criteria, edge cases, and definition of done.

mohitagw15856github.com/mohitagw15856GitHub ↗
claude-codecursorMIT
Install
npx skills add mohitagw15856/pm-claude-skills --skill user-story-writer --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 4
SKILL.md size: 11 KB
Bundled scripts: none
Path: skills/user-story-writer/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,255
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# User Story Writer Skill This skill produces production-ready user stories from a feature brief, PRD section, or verbal description. Each story follows the standard format with a clear who/what/why, behavioural acceptance criteria in Given/When/Then format, edge cases, and definition of done. Output is ready to paste into Jira, Linear, or your planning tool. ## Required Inputs Ask the user for these if not provided: - **Feature or change** to break into stories — paste the brief, PRD section, or describe the feature - **User types / personas** involved (e.g. admin, end user, guest, API consumer) - **Scope** — are we writing one story or decomposing an epic into a full set of stories? - **Acceptance criteria format preference** — Given/When/Then, bullet checklist, or both? - **Technical constraints or notes** — anything the engineering team has flagged that should shape the stories ## Output Structure For each story: --- ## Story: [Short title — verb + noun, e.g. "Filter search results by date range"] **Epic:** [Parent epic name — e.g. "Advanced Search"] **Story ID:** [Jira/Linear ID — leave blank if not yet created] **Priority:** [P1 / P2 / P3] **Story points:** [Leave blank — for

What's inside
Steps it walks through
  1. Required Inputs
  2. Output Structure
  3. Story: [Short title — verb + noun, e.g. "Filter search results by date range"]
  4. User Story
  5. Context
  6. Acceptance Criteria
  7. Edge Cases
  8. Out of Scope
  9. Definition of Done
  10. Epic Decomposition Template
  11. Common Story Anti-Patterns — and Fixes
  12. Example: Full Story Set for a Feature
  13. Story 1: Export invoice list as CSV
  14. Story 2: Export invoice list as PDF
Ships with 3 files
  • references/acceptance-criteria-craft.md
  • references/worked-example.md
  • templates/story-card.md
More from pm-claude-skills
All skills →
About this skill
What does the user-story-writer skill do?

Write well-structured user stories with acceptance criteria and edge cases. Use when asked to write user stories, create tickets from a feature brief, convert a PRD into stories, or write acceptance criteria. Produces ready-to-estimate stories in the standard format with clear acceptance criteria, edge cases, and definition of done.

How do I install it?

Run `npx skills add mohitagw15856/pm-claude-skills --skill user-story-writer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going