user-storieslisted

# User Story Generator Write user stories for the feature: **$ARGUMENTS** (format defaults to standard) ## Steps 1. **Understand the feature** — If a codebase exists, read the relevant code to understand current state. If it's a new feature, work from the description. 2. **Identify personas** — Who uses this feature? - Primary user (the main beneficiary) - Secondary users (admin, support, other roles) - System actors (cron jobs, webhooks, integrations) 3. **Write user stories** — For each meaningful interaction: ### Standard format ``` As a <persona>, I want to <action>, so that <benefit>. ``` ### Acceptance criteria ``` Given <precondition>, When <action>, Then <expected result>. ``` 4. **Categorize stories**: - **Must have**: core functionality, the feature doesn't work without these - **Should have**: expected behavior, users would notice if missing - **Could have**: nice to have, can be deferred - **Won't have** (this iteration): explicitly out of scope 5. **Add technical notes** where relevant: - API endpoints needed - Database changes - Third-party integrations - Performance considerations ## Output Format ```markdown ## User Stories: <feature> ### Personas - **<Persona 1>**: <description> - **<Persona 2>**: <description> --- ### Must Have #### US-001: <title> **As a** <persona>, **I want to** <action>, **so that** <benefit>. **Acceptance Criteria**: - [ ] Given <condition>, when <action>, then <result> - [ ] Given <condi