INVEST User Stories

User stories

by phuryn · MIT license · ★ 26,557 on GitHub · updated Sep 14

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…

---
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

Overview

Create user stories following the 3 C's (Card, Conversation, Confirmation) and INVEST criteria. Generates stories with descriptions, design links, and acceptance criteria.

What you get

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

Manual install (npx, ZIP)

Claude Codenpx skills add phuryn/pm-skills --skill user-stories -g -a claude-code

Claude Code (degit)npx degit phuryn/pm-skills/pm-execution/skills/user-stories#main ~/.claude/skills/user-stories

Claude.ai / desktopZip the folder and upload it under Settings → Capabilities → Skills.

Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

SKILL.md2.9 KB

Read SKILL.md here

phuryn/main1 file shown

SKILL.md2.9 KB

Browse every file on GitHub↗

SKILL.md

Show the full text75 lines

user-stories/SKILL.md75 lines · 2.9 KB

PreviewCode

Outline

RawView on GitHub

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

1	---
2	name: user-stories
3	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."
4	---
5	# User Stories
6
7	Create user stories following the 3 C's (Card, Conversation, Confirmation) and INVEST criteria. Generates stories with descriptions, design links, and acceptance criteria.
8
9	Use when: Writing user stories, breaking down features into stories, creating backlog items, or defining acceptance criteria.
10
11	Arguments:
12	- `$PRODUCT`: The product or system name
13	- `$FEATURE`: The new feature to break into stories
14	- `$DESIGN`: Link to design files (Figma, Miro, etc.)
15	- `$ASSUMPTIONS`: Key assumptions or context
16
17	## Step-by-Step Process
18
19	1. Analyze the feature based on provided design and context
20	2. Identify user roles and distinct user journeys
21	3. Apply 3 C's framework:
22	- Card: Simple title and one-liner
23	- Conversation: Detailed discussion of intent
24	- Confirmation: Clear acceptance criteria
25	4. Respect INVEST criteria: Independent, Negotiable, Valuable, Estimable, Small, Testable
26	5. Use plain language a primary school graduate can understand
27	6. Link to design files for visual reference
28	7. Output user stories in structured format
29
30	## Story Template
31
32	Title: [Feature name]
33
34	Description: As a [user role], I want to [action], so that [benefit].
35
36	Design: [Link to design files]
37
38	Acceptance Criteria:
39	1. [Clear, testable criterion]
40	2. [Observable behavior]
41	3. [System validates correctly]
42	4. [Edge case handling]
43	5. [Performance or accessibility consideration]
44	6. [Integration point]
45
46	## Example User Story
47
48	Title: Recently Viewed Section
49
50	Description: As an Online Shopper, I want to see a 'Recently viewed' section on the product page to easily revisit items I considered.
51
52	Design: [Figma link]
53
54	Acceptance Criteria:
55	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.
56	2. It is not displayed for users visiting the first product page of their session.
57	3. The current product itself is excluded from the displayed items.
58	4. The section showcases product cards or thumbnails with images, titles, and prices.
59	5. Each product card indicates when it was viewed (e.g., 'Viewed 5 minutes ago').
60	6. Clicking on a product card leads the user to the corresponding product page.
61
62	## Output Deliverables
63
64	- Complete set of user stories for the feature
65	- Each story includes title, description, design link, and 4-6 acceptance criteria
66	- Stories are independent and can be developed in any order
67	- Stories are sized for one sprint cycle
68	- Stories reference related design documentation
69
70	---
71
72	### Further Reading
73
74	- [How to Write User Stories: The Ultimate Guide](https://www.productcompass.pm/p/how-to-write-user-stories)
75