use-caselisted

## What this skill does Produces a complete use case following the Cockburn/RUP format. A use case describes a goal-directed interaction between an actor and the system — capturing not just the happy path, but the extension flows (error, alternative, and exception paths) that user stories typically omit. ## When to use it - User asks to "write a use case" or needs more rigorous specification than a user story. - The interaction involves complex branching, multiple actors, or system-to-system calls. - The requirement must satisfy a compliance, audit, or contractual standard that demands formal documentation. - User is breaking down a user story that is too complex to estimate because its edge cases are unknown. - Use cases are being collected for a system specification or `requirements-document`. ## Key concepts ### Use case vs. user story | | User story | Use case | | --- | --- | --- | | **Format** | Persona / want / benefit | Goal / actors / flows | | **Scope** | One sprint | One interaction goal | | **Detail** | Acceptance criteria | Full flow + all extensions | | **Audience** | Agile team | Analyst, architect, tester | | **Best for** | Feature cards, backlog | Complex interactions, specs | ### Use case components | Component | Description | | --- | --- | | **Use case ID** | Unique identifier (e.g., UC-001) | | **Name** | Active verb + noun (e.g., "Place order", "Reset password") | | **Goal** | The outcome the primary actor wants to achieve | | **Primary actor** | W