user-stories

1# User Stories
2 
3Create 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 
151. **Analyze the feature** based on provided design and context
162. **Identify user roles** and distinct user journeys
173. **Apply 3 C's framework:**
18   - Card: Simple title and one-liner
19   - Conversation: Detailed discussion of intent
20   - Confirmation: Clear acceptance criteria
214. **Respect INVEST criteria:** Independent, Negotiable, Valuable, Estimable, Small, Testable
225. **Use plain language** a primary school graduate can understand
236. **Link to design files** for visual reference
247. **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:**
351. [Clear, testable criterion]
362. [Observable behavior]
373. [System validates correctly]
384. [Edge case handling]
395. [Performance or accessibility consideration]
406. [Integration point]
41 
42## Example User Story
43…