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