Creates INVEST-compliant user stories with acceptance criteria. Use when capturing requirements, defining backlog items, or breaking down features.
This skill inherits all available tools. When active, it can use any tool Claude has access to.
Create user stories meeting INVEST criteria.
templates/user-story.md template[bracketed placeholders]CREATE: No existing story path → Copy template, generate next ID, fill sections
EDIT: Path provided → Read existing, preserve ID, update as requested
As a [type of user],
I want [goal/desire],
So that [benefit/value].
Example:
As a registered customer,
I want to save items to a wishlist,
So that I can purchase them later without searching again.
Title - Short, descriptive. "Wishlist - Add Items" not "User feature for saving stuff"
User Story Statement - Who (role), What (goal), Why (value)
Acceptance Criteria - Specific, testable conditions with Given-When-Then or checklist format
| Criterion | Meaning |
|---|---|
| Independent | Develop in any order |
| Negotiable | Details discussable |
| Valuable | Delivers user/business value |
| Estimable | Team can size it |
| Small | Fits in one sprint |
| Testable | Clear acceptance criteria |
Given-When-Then (preferred):
- [ ] Given [precondition], When [action], Then [result]
Checklist:
- [ ] User can [action with measurable outcome]
Be specific about user roles: "premium subscriber" not "user"
Focus on outcomes: "export my data" not "a button"
State the benefit: "analyze in Excel" not "click it"
Split large stories by: workflow steps, business rules, data variations, user roles, or CRUD operations.
Do not write technical stories ("As a developer..."). Do not combine multiple features. Do not describe implementation. Do not omit the value clause. Do not use vague criteria.
| Type | Purpose |
|---|---|
| Story | New user-facing capability |
| Task | Technical work, no direct user value |
| Bug | Fix broken behavior |
stories/
├── US-001-brief-description.md
├── US-002-brief-description.md
└── archive/
Create stories/ if needed. Scan for existing US-*.md files, find highest number, increment, pad to 3 digits.
Use templates/user-story.md for all new stories.
After creating/editing, report: file path, Story ID, acceptance criteria count, any INVEST concerns.