use-case

Draft use-case specifications from user stories using a structured template.

3|1|Updated Jan 13, 2026
One-click install
npx skills add https://github.com/sirius-cc-wu/sirius-skills --skill use-case-sirius-cc-wu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: use-case
Source: https://github.com/sirius-cc-wu/sirius-skills/tree/main/use-case
Command: npx skills add https://github.com/sirius-cc-wu/sirius-skills --skill use-case-sirius-cc-wu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This skill provides a structured, repeatable approach to turning user stories into formal use-case specifications, reducing ambiguity and speeding up review and validation.

Core Features & Use Cases

  • Structured Elaboration: Converts a target user story into a complete use case with Goal, Actors, Preconditions, Main Success Scenario, Alternative Flows, Postconditions, and Test Cases.
  • Template-Driven: Uses the assets/use-case-template.md to ensure a consistent format across all use cases.
  • Linkage & Traceability: Creates a new file named use-case-<story-name>.md within the relevant specs directory and links it back to the original story for traceability.

Quick Start

Identify a target story in spec.md and create a new file named use-case-<story-name>.md in specs/<ID>-<name>/, copy the template, and fill out all sections.

Frequently Asked Questions about use-case

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

FAQPage Schema
What is a use-case specification and when do I need one for product development?

A use-case specification is a structured document detailing goals, actors, preconditions, main flows, and postconditions. You need one to reduce ambiguity and speed up review when turning user stories into formal product requirements.

How do I generate detailed use cases from a user story?

To generate detailed use cases from user stories, identify the target story in your spec.md, create a use-case-<story-name>.md file, and populate the use-case template with actors, main success scenarios, and test cases.

How do I maintain traceability between use-case files and original requirements?

Maintain traceability by creating the use-case-<story-name>.md file within the relevant specs directory and linking it back to the original story, ensuring consistent structure for validation and review.

Does this use-case template include alternate flows and test cases?

Yes, the use-case template includes sections for alternative flows and test cases, alongside goals, actors, preconditions, main success scenarios, and postconditions, ensuring complete specification coverage.

What is the best way to structure use-case documentation for consistent review?

The best way to structure use-case documentation is using a template-driven approach. Applying a standardized template ensures consistent format across all use-case files, reducing ambiguity and speeding up validation.