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
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# User Stories67Create user stories following the 3 C's (Card, Conversation, Confirmation) and INVEST criteria. Generates stories with descriptions, design links, and acceptance criteria.89**Use when:** Writing user stories, breaking down features into stories, creating backlog items, or defining acceptance criteria.1011**Arguments:**12- `$PRODUCT`: The product or system name13- `$FEATURE`: The new feature to break into stories14- `$DESIGN`: Link to design files (Figma, Miro, etc.)15- `$ASSUMPTIONS`: Key assumptions or context1617## Step-by-Step Process18191. **Analyze the feature** based on provided design and context202. **Identify user roles** and distinct user journeys213. **Apply 3 C's framework:**22 - Card: Simple title and one-liner23 - Conversation: Detailed discussion of intent24 - Confirmation: Clear acceptance criteria254. **Respect INVEST criteria:** Independent, Negotiable, Valuable, Estimable, Small, Testable265. **Use plain language** a primary school graduate can understand276. **Link to design files** for visual reference287. **Output user stories** in structured format2930## Story Template3132**Title:** [Feature name]3334**Description:** As a [user role], I want to [action], so that [benefit].3536**Design:** [Link to design files]3738**Acceptance Criteria:**391. [Clear, testable criterion]402. [Observable behavior]413. [System validates correctly]424. [Edge case handling]435. [Performance or accessibility consideration]446. [Integration point]4546## Example User Story4748**Title:** Recently Viewed Section4950**Description:** As an Online Shopper, I want to see a 'Recently viewed' section on the product page to easily revisit items I considered.5152**Design:** [Figma link]5354**Acceptance Criteria:**551. The 'Recently viewed' section is displayed at the bottom of the product page for every user who has previously viewed at least 1 product.562. It is not displayed for users visiting the first product page of their session.573. The current product itself is excluded from the displayed items.584. The section showcases product cards or thumbnails with images, titles, and prices.595. Each product card indicates when it was viewed (e.g., 'Viewed 5 minutes ago').606. Clicking on a product card leads the user to the corresponding product page.6162## Output Deliverables6364- Complete set of user stories for the feature65- Each story includes title, description, design link, and 4-6 acceptance criteria66- Stories are independent and can be developed in any order67- Stories are sized for one sprint cycle68- Stories reference related design documentation6970---7172### Further Reading7374- [How to Write User Stories: The Ultimate Guide](https://www.productcompass.pm/p/how-to-write-user-stories)
peteedoo