user-stories
Writes user stories using the 3 C's and INVEST criteria, with descriptions, design links and acceptance criteria.
- Kind
- Skill
- Works with
- Claude Code, Cursor
- Source
- PM Skills (Pawel Huryn) @ 2a12295a7717
- Path
- pm-execution/skills/user-stories/SKILL.md
- Jobs
- Planning, Documentation
- Topics
- Product management
Credit
- Made by
- phuryn
- Original
- github.com/phuryn/pm-skills/blob/2a12295a7717569baa7be181b4cf…
- License
- MIT
Listed by Skill Manifest; not made by us.
InstallInstall it from a plugin marketplace.
claude plugin install pm-execution@pm-skills
Install factsScanned 2 Nov 2026
- Adds
- .claude/skills/user-stories/ (the skill folder)
- Runs scripts
- None found
- Uses the network
- None found
- Needs secrets
- None found
- Reads environment variables
- PRODUCT
- FEATURE
- DESIGN
- ASSUMPTIONS
- Source revision
- 2a12295a7717
- Licence
- MIT
- Last activity
- 29 Oct 2026
- Review
- Reviewed
Found by a static scan of the stored text; nothing is run. “None found” is not a guarantee, so read what you install before you run it.
- Only the main file is read; other files in the folder are not scanned
# 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 1. **Analyze the feature** based on provided design and context 2. **Identify user roles** and distinct user journeys 3. **Apply 3 C's framework:** - Card: Simple title and one-liner - Conversation: Detailed discussion of intent - Confirmation: Clear acceptance criteria 4. **Respect INVEST criteria:** Independent, Negotiable, Valuable, Estimable, Small, Testable 5. **Use plain language** a primary school graduate can understand 6. **Link to design files** for visual reference 7. **Output user stories** in structured format ## Story Template **Title:** [Feature name] …