From backend-development
Create structured use case documentation with sequence diagrams for backend systems. Use when documenting API endpoints, service interactions, event flows, or system behaviors. Triggers on requests like "document this use case", "create use case for X endpoint", "write flow documentation", or "explain how X feature works".
How this skill is triggered — by the user, by Claude, or both
Slash command
/backend-development:writing-use-casesThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Create use case markdown files that document backend flows with mermaid sequence diagrams.
Create use case markdown files that document backend flows with mermaid sequence diagrams.
# {Feature Name} Use Case
## Overview
{1-2 sentences: what this use case does and when it's triggered}
## Flow
{mermaid sequence diagram - see references/mermaid-patterns.md}
## Key Points
- **Entry Point:** `{HTTP method} {path}` ([`{ControllerName}`]({relative-path}))
- **Request Model:** [`{DtoName}`]({relative-path})
- **State Transition:** {from} → {to}
- **Event:** `{EventName}` published to {destination}
- **Validation:** {key validation rules}
docs/{use case name}-use-case.md as output file location (DEFAULT).Note over blocksalt/else for conditional flowsSee references/mermaid-patterns.md for sequence diagram syntax and examples.
npx claudepluginhub mixomat/claude-plugins --plugin backend-developmentDocuments a single runtime scenario as a structured Flow file under flows/<topic>/ with context, one Mermaid diagram, step-by-step branches, and source references so end-to-end service behavior is visible at a glance.
Adds Mermaid sequenceDiagram blocks to the SAD's runtime view (sad.md §6) for critical flows, with happy and error paths. Reads participants from §5, writes diagrams one flow at a time after user confirmation.
Authors Use Case 2.0 specifications to capture functional requirements and actor-system interactions using structured templates for preconditions, flows, and postconditions. Useful for agile requirements documentation.