User Stories
- 2.2k installs
- 24.9k repo stars
- Updated July 3, 2026
- phuryn/pm-skills
user-stories is an agent skill that Create user stories following the 3 C's (Card, Conversation, Confirmation) and INVEST criteria with descriptions, design.
About
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 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 Description As a user role I want to action so that benefit
- description: "Create user stories following the 3 C's (Card, Conversation, Confirmation) and INVEST criteria with descri
- Create user stories following the 3 C's (Card, Conversation, Confirmation) and INVEST criteria. Generates stories with d
- **Use when:** Writing user stories, breaking down features into stories, creating backlog items, or defining acceptance
- Follow user-stories SKILL.md steps and documented constraints.
- Follow user-stories SKILL.md steps and documented constraints.
User Stories by the numbers
- 2,221 all-time installs (skills.sh)
- +98 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #500 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
user-stories capabilities & compatibility
- Capabilities
- description: "create user stories following the · create user stories following the 3 c's (card, c · **use when:** writing user stories, breaking dow · follow user stories skill.md steps and documente
- Use cases
- orchestration
What user-stories says it does
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, br
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.
npx skills add https://github.com/phuryn/pm-skills --skill user-storiesAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 2.2k |
|---|---|
| repo stars | ★ 24.9k |
| Security audit | 3 / 3 scanners passed |
| Last updated | July 3, 2026 |
| Repository | phuryn/pm-skills ↗ |
When should an agent use user-stories and what problem does it solve?
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 fe
Who is it for?
Developers invoking user-stories as documented in the skill source.
Skip if: Skip when requirements fall outside user-stories documented scope.
When should I use this skill?
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 fe
What you get
Outputs aligned with the user-stories SKILL.md workflow and stated deliverables.
- user story cards
- acceptance criteria
By the numbers
- Applies the 3 C's framework: Card, Conversation, Confirmation
- Enforces INVEST criteria across generated stories
Files
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]
Description: As a [user role], I want to [action], so that [benefit].
Design: [Link to design files]
Acceptance Criteria: 1. [Clear, testable criterion] 2. [Observable behavior] 3. [System validates correctly] 4. [Edge case handling] 5. [Performance or accessibility consideration] 6. [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: 1. The 'Recently viewed' section is displayed at the bottom of the product page for every user who has previously viewed at least 1 product. 2. It is not displayed for users visiting the first product page of their session. 3. The current product itself is excluded from the displayed items. 4. The section showcases product cards or thumbnails with images, titles, and prices. 5. Each product card indicates when it was viewed (e.g., 'Viewed 5 minutes ago'). 6. 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
Related skills
Setup Matt Pocock SkillsScaffold the per-repo configuration that Matt Pocock’s engineering agent skills rely on so they understand the issue tracker, triage labels, and domain documentation la495k196k
Lark AppsConnect Claude, Cursor or custom agents directly to Lark (Feishu) for messaging, document automation, approval workflows and enterprise data access.402k
CavemanSlash token usage by roughly 75% while keeping every technical detail intact when working with Claude Code, Cursor or similar agents.391k94.7k
Lark Skill MakerQuickly turn any Lark/Feishu OpenAPI call or multi-step workflow into a reusable agent skill with its own SKILL.md.386k16k
Running Claude Code Via Litellm CopilotRun Claude Code at a fraction of the cost by routing requests through LiteLLM to the GitHub Copilot Chat API.270k72
Codex PetGenerate a complete Codex Pet spritesheet and metadata from one reference image without needing an OpenAI key or Codex Pro.246k10FAQ
What is 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 stori
When should I use 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 stori
Is user-stories safe to install?
Review the Security Audits panel on this page before production use.