user-story-writer

Solid

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.

Data & Documents 915 stars 165 forks Updated 3 days ago MIT

Install

View on GitHub

Quality Score: 93/100

Stars 20%
99
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# 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 engineering to estimate] --- ### User Story > **As a** [specific user type — not "user"], > **I want to** [concrete action they want to take], > **So that** [the outcome they achieve — business value, not feature description]. **Example:** > As an **account manager**, > I want to **filt...

Details

Author
mohitagw15856
Repository
mohitagw15856/pm-claude-skills
Created
4 months ago
Last Updated
3 days ago
Language
Shell
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

user-story-writer

Generate and validate user stories from requirements with INVEST validation and acceptance criteria

1,034 Updated today
a5c-ai
AI & Automation Listed

user-story-creation

This skill should be used when the user asks to "create user stories", "write user stories", "break down epic into stories", "define user stories", "what stories do I need", "apply INVEST criteria", "write acceptance criteria", "split a large story", "story is too big", "story splitting", or when decomposing epics into specific, valuable user stories.

1 Updated today
mamiaijf
AI & Automation Solid

user-stories

Create user stories following the 3 C's (Card, Conversation, Confirmation) and INVEST criteria with descriptions, design links, and acceptance criteria. Use when writing user stories, breaking down features into backlog items, or defining acceptance criteria.

11,758 Updated 1 weeks ago
phuryn
AI & Automation Solid

user-story-generator

Generate and validate user stories from various inputs including requirements, research, and feature descriptions. Apply INVEST criteria validation, create acceptance criteria, split large stories, and convert between story formats.

1,034 Updated today
a5c-ai
AI & Automation Solid

014-agile-user-story

Guides the creation of agile user stories and Gherkin feature files. Use when the user wants to create a user story, write acceptance criteria, define Gherkin scenarios, or author BDD feature files. This should trigger for requests such as Create a user story; Write a user story; I need to write a user story. Part of cursor-rules-java project

393 Updated today
jabrena