user-stories

Name: user-stories
Author: phuryn

2.0kinstalls2.5kforks

How to install user-stories?

phuryn/pm-skills/user-stories

$npx -y skills add phuryn/pm-skills --skill user-stories

Installs into the current project.

Summary

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.

Files · 1

View on GitHub

SKILL.md

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

People who liked this also viewed

6 picks

Type

user-stories

2.0kinstalls2.5kforks

View on GitHub

How to install user-stories?

phuryn/pm-skills/user-stories

$npx -y skills add phuryn/pm-skills --skill user-stories

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

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

People who liked this also viewed

6 picks

Type