Break product scope into user stories with clear acceptance criteria. — Claude Skill
A Claude Skill for Claude Code by Paweł Huryn — run /write-stories in Claude·Updated Jun 13, 2026·vmain@d384f0c
Converts features, designs, and PRD context into small user stories using the 3 Cs and INVEST criteria, with testable acceptance criteria, edge cases, and sprint-readiness notes.
- Turns a feature or PRD into stories that explain who needs what and why.
- Uses Card, Conversation, and Confirmation so stories carry intent, not just tasks.
- Applies INVEST criteria so stories stay independent, small, valuable, and testable.
- Writes acceptance criteria, edge cases, and out-of-scope notes that QA, design, and engineering can verify.
The team creates a large ticket called “Build onboarding checklist,” then discovers edge cases during implementation.
Run /write-stories to split the feature into user-centered stories with clear acceptance criteria before sprint planning.
Who this is for
What it does
Break a feature into sprint-sized stories with acceptance criteria.
Turn Figma flows and PRD notes into implementation-ready backlog items.
Make the expected behavior testable before engineering starts.
How it works
Read the feature, PRD, design link, user roles, and assumptions.
Identify distinct user journeys and split the work into independent stories.
Write each story as user, action, and benefit.
Add acceptance criteria covering normal behavior, edge cases, validation, accessibility, and integrations.
Flag stories that are too large, blocked by missing decisions, or not ready for sprint planning.
Input options
The scope that needs to become backlog items.
Example
Feature: onboarding checklist for new workspace admins. Users: workspace admin, invited teammate, support agent. Rules: show checklist only during first 14 days; reminders can be sent once per teammate per day; completed tasks should not distract; support needs event history.
**Title:** Admin sees setup progress **User story:** As a workspace admin, I want to see incomplete setup steps so that I know what is blocking activation. **Conversation:** The checklist is an onboarding aid, not a permanent dashboard.
1. Checklist appears only for workspaces less than 14 days old. 2. Current activation blocker appears first. 3. Completed tasks are marked complete or visually de-emphasized. 4. If all tasks are complete, the empty state says setup is done. 5. Checklist is usable with keyboard navigation and screen readers.
**Title:** Admin sends teammate invite reminder **User story:** As a workspace admin, I want to remind invited teammates from the checklist so setup does not stall. **Acceptance criteria:** reminder appears only for pending invites; one reminder per teammate per day; success/failure message is visible; reminder event is logged.
| Criterion | Status | |---|---| | Independent | Progress view and reminder can ship separately | | Valuable | Both support activation goal | | Small | Each story fits a sprint | | Testable | Acceptance criteria cover normal, edge, and accessibility cases |
Metrics this improves
Works with
Want to use User Stories?
Choose how to get started.
Install and run this skill locally on your computer.
Open a terminal on your computer and paste this command:
This downloads the skill with all its files to your computer:
Add -g at the end to make it available in all your projects.
Start Claude Code, then type the command:
User Stories
Create user stories following the 3 C's (Card, Conversation, Confirmation) and INVEST criteria. Generates stories with descriptions, design links, and acceptance criteria.
Use when: Writing user stories, breaking down features into stories, creating backlog items, or defining acceptance criteria.
Arguments:
$PRODUCT: The product or system name$FEATURE: The new feature to break into stories$DESIGN: Link to design files (Figma, Miro, etc.)$ASSUMPTIONS: Key assumptions or context
Step-by-Step Process
- Analyze the feature based on provided design and context
- Identify user roles and distinct user journeys
- Apply 3 C's framework:
- Card: Simple title and one-liner
- Conversation: Detailed discussion of intent
- Confirmation: Clear acceptance criteria
- Respect INVEST criteria: Independent, Negotiable, Valuable, Estimable, Small, Testable
- Use plain language a primary school graduate can understand
- Link to design files for visual reference
- Output user stories in structured format
Story Template
Title: [Feature name]
Description: As a [user role], I want to [action], so that [benefit].
Design: [Link to design files]
Acceptance Criteria:
- [Clear, testable criterion]
- [Observable behavior]
- [System validates correctly]
- [Edge case handling]
- [Performance or accessibility consideration]
- [Integration point]
Example User Story
Title: Recently Viewed Section
Description: As an Online Shopper, I want to see a 'Recently viewed' section on the product page to easily revisit items I considered.
Design: [Figma link]
Acceptance Criteria:
- The 'Recently viewed' section is displayed at the bottom of the product page for every user who has previously viewed at least 1 product.
- It is not displayed for users visiting the first product page of their session.
- The current product itself is excluded from the displayed items.
- The section showcases product cards or thumbnails with images, titles, and prices.
- Each product card indicates when it was viewed (e.g., 'Viewed 5 minutes ago').
- Clicking on a product card leads the user to the corresponding product page.
Output Deliverables
- Complete set of user stories for the feature
- Each story includes title, description, design link, and 4-6 acceptance criteria
- Stories are independent and can be developed in any order
- Stories are sized for one sprint cycle
- Stories reference related design documentation
Further Reading
Reference documents
name: user-stories description: "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."
User Stories
Create user stories following the 3 C's (Card, Conversation, Confirmation) and INVEST criteria. Generates stories with descriptions, design links, and acceptance criteria.
Use when: Writing user stories, breaking down features into stories, creating backlog items, or defining acceptance criteria.
Arguments:
$PRODUCT: The product or system name$FEATURE: The new feature to break into stories$DESIGN: Link to design files (Figma, Miro, etc.)$ASSUMPTIONS: Key assumptions or context
Step-by-Step Process
- Analyze the feature based on provided design and context
- Identify user roles and distinct user journeys
- Apply 3 C's framework:
- Card: Simple title and one-liner
- Conversation: Detailed discussion of intent
- Confirmation: Clear acceptance criteria
- Respect INVEST criteria: Independent, Negotiable, Valuable, Estimable, Small, Testable
- Use plain language a primary school graduate can understand
- Link to design files for visual reference
- Output user stories in structured format
Story Template
Title: [Feature name]
Description: As a [user role], I want to [action], so that [benefit].
Design: [Link to design files]
Acceptance Criteria:
- [Clear, testable criterion]
- [Observable behavior]
- [System validates correctly]
- [Edge case handling]
- [Performance or accessibility consideration]
- [Integration point]
Example User Story
Title: Recently Viewed Section
Description: As an Online Shopper, I want to see a 'Recently viewed' section on the product page to easily revisit items I considered.
Design: [Figma link]
Acceptance Criteria:
- The 'Recently viewed' section is displayed at the bottom of the product page for every user who has previously viewed at least 1 product.
- It is not displayed for users visiting the first product page of their session.
- The current product itself is excluded from the displayed items.
- The section showcases product cards or thumbnails with images, titles, and prices.
- Each product card indicates when it was viewed (e.g., 'Viewed 5 minutes ago').
- Clicking on a product card leads the user to the corresponding product page.
Output Deliverables
- Complete set of user stories for the feature
- Each story includes title, description, design link, and 4-6 acceptance criteria
- Stories are independent and can be developed in any order
- Stories are sized for one sprint cycle
- Stories reference related design documentation