use-case

Write structured use case specifications with triggers, flows, and exceptions.

23|1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/jdm4pku/RE-Skills --skill use-case-jdm4pku
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: use-case
Source: https://github.com/jdm4pku/RE-Skills/tree/main/skills/use-case
Command: npx skills add https://github.com/jdm4pku/RE-Skills --skill use-case-jdm4pku

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? User stories are often too brief to capture complex user-system interactions, branching logic, and error handling, leaving developers to invent exception behavior at coding time. This Skill guides the creation of detailed use case specifications that document actors, preconditions, triggers, normal flows, alternative flows, exceptions, and postconditions. ## Core Features & Use Cases - Structured Use Case Authoring: Step-by-step process covering identification, normal flow writing, alternative flow discovery, exception definition, and pre/postcondition specification. - Fill-in Template and Worked Examples: Includes a reusable markdown template plus a complete pharmacy prescription example showing well-written and anti-pattern use cases. - Quality Review Checklist: Built-in checks for actor clarity, technology-neutral steps, exception coverage, and appropriate use case granularity. - Use Case: When specifying how a pharmacist processes a prescription with drug interaction checks, inventory validation, and printer failure handling, use this Skill to produce a complete UC specification with all branching paths documented. ## Quick Start Ask the agent to write a use case specification for a specific user goal, such as documenting how a lab technician adds a chemical to inventory including all alternative flows and exceptions.

Frequently Asked Questions about use-case

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a use case specification?▼

Identify the user goal and primary actor, then write the normal flow as numbered actor-system exchange steps. Add alternative flows for valid variations, exceptions for error conditions, and define preconditions and postconditions. Keep the normal flow to 7-12 steps.

What is the difference between a use case and a user story?▼

User stories are brief one-to-three sentence descriptions suited for agile backlogs, while use cases provide detailed step-by-step flows with comprehensive exception handling. Escalate to use cases when interactions have three or more alternative flows or the domain requires detailed error documentation.

When should I use use cases instead of user stories?▼

Use use cases for complex interaction sequences, branching logic, or systems with regulatory, safety, or high-reliability requirements. Start with user stories and escalate when the story cannot capture the exception handling or flow complexity.

Why do use cases need exception flows?▼

Without documented exceptions, developers invent error handling inconsistently at coding time and testers lack a basis for negative test cases. For every normal flow step, ask what could go wrong and document at least two to three exceptions per use case.

What are common use case writing mistakes?▼

Common pitfalls include omitting exceptions, embedding UI implementation details in steps, writing flows longer than 12 steps, and treating internal system components as actors. Keep steps technology-neutral and split oversized use cases at natural breakpoints.