write-user-storylisted

## What this skill does Produces a complete, ready-to-groom user story following the standard Atlassian/agile format. It applies the INVEST criteria and the 3 Cs framework (Card, Conversation, Confirmation) to ensure each story is well-scoped, valuable, and testable — not just syntactically correct. **Reference:** Atlassian — [User stories with examples and a template](https://www.atlassian.com/agile/project-management/user-stories) ## When to use it - User asks to "write a user story" or "create a story" for a feature or requirement. - User wants to refine a rough idea, acceptance note, or bug description into a proper story. - User needs to validate whether an existing story is well-formed. - User is decomposing an epic into individual stories. ## Key concepts ### The standard format (Connextra template) ``` As a [persona], I want to [action / capability], so that [benefit / outcome]. ``` - **Persona** — who benefits (not "user" generically — use a real role: "logged-in customer", "warehouse operator", "admin"). - **Want** — the capability or action, not the implementation ("I want to filter results" not "I want a dropdown"). - **Benefit** — the why; if the benefit is obvious, keep it short but never omit it. ### INVEST criteria A well-formed story is: | Letter | Criterion | What to check | | --- | --- | --- | | **I** | Independent | Can be developed without another story blocking it? | | **N** | Negotiable | Is it a conversation-starter, not a contract? | | **V*