user-stories

# 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 1. **Analyze the feature** based on provided design and context 2. **Identify user roles** and distinct user journeys 3. **Apply 3 C's framework:** - Card: Simple title and one-liner - Conversation: Detailed discussion of intent - Confirmation: Clear acceptance criteria 4. **Respect INVEST criteria:** Independent, Negotiable, Valuable, Estimable, Small, Testable 5. **Use plain language** a primary school graduate can understand 6. **Link to design files** for visual reference 7. **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:** 1. [Clear, testable criterion] 2. [Observable behavior] 3. [System validates correctly] 4. [Edge case handling] 5. [Performance or accessibility consideration] 6. [Integration point] ## Example User Story **Title:** Recently...