Stats
Actions
Tags
From aiup-core
Generates detailed use case specification documents covering actors, preconditions, main/alternative flows, postconditions, and business rules. Useful for documenting system behaviors and functional specs.
How this skill is triggered — by the user, by Claude, or both
Slash command
/aiup-core:use-case-specThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Create or update use case specification documents for $ARGUMENTS in `docs/use_cases/`. Each use case describes a complete interaction between an actor and the system to achieve a goal.
Create or update use case specification documents for $ARGUMENTS in docs/use_cases/. Each use case describes a complete interaction between an actor and the system to achieve a goal.
Use templates/use-case.md as the document structure.
Use Case ID: UC-001 Use Case Name: Create Reservation Primary Actor: Front Desk Clerk Goal: Create a new room reservation for a guest Status: Approved
Trigger: Guest email matches existing record (step 3) Flow:
Trigger: No rooms available for selected dates (step 5) Flow:
Trigger: Business rule requires deposit (step 8) Flow:
Reservations must be for at least one night.
Reservations cannot be made more than 365 days in advance.
Reservations of 3 or more nights require a 50% deposit.
npx claudepluginhub ai-unified-process/marketplace --plugin aiup-coreAuthors 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.
Generates Cockburn fully-dressed use case documents describing app behavior from actor perspectives, creating use-cases/ directory with MD files and README index.
Guides use case authoring and decomposition via Cockburn's 12-step process and Jacobson UC 2.0 levels. Creates YAML artifacts validated against schema, INVEST-checked slices, and interaction sequences for test specs and contracts.