Skill
use-case-diagram
Creates or updates PlantUML use case diagrams defining actors, use cases, and their relationships from requirements. Use when the user asks to "create a use case diagram", "draw a UML diagram", "map actors to use cases", "generate a .puml file", or mentions PlantUML, use case overview, actor diagram, or system use cases.
From aiup-coreInstall
1
Run in your terminal$
npx claudepluginhub martinellich/aiup-marketplace --plugin aiup-coreTool Access
This skill uses the workspace's default tool permissions.
Skill Content
Use Case Diagram
Instructions
Create or update the PlantUML use case diagram at docs/use_cases.puml based on docs/requirements.md.
DO NOT
- Create diagrams without reading the requirements first
- Use non-standard PlantUML syntax
- Include implementation details in use case names
Template
@startuml Use Cases Overview
left to right direction
actor "User" as user
actor "Administrator" as admin
rectangle "System Name" {
usecase "UC-001\nDescription" as UC001
usecase "UC-002\nDescription" as UC002
usecase "UC-003\nDescription" as UC003
}
admin --> UC001
user --> UC002
user --> UC003
@enduml
Conventions
- Each use case has a unique id and a description
- Use Case ID: UC-{3-digit} (UC-001, UC-002, ...)
- Each use case should trace to at least one functional requirement
- Add notes sparingly, only where relationships need clarification
Workflow
- Read the requirements at
docs/requirements.md - Read existing diagram at
docs/use_cases.puml(if exists) - Identify actors and use cases from requirements
- Create/update the PlantUML use case diagram
- Validate the diagram:
- Each use case traces to at least one functional requirement in
docs/requirements.md - All actors are connected to at least one use case
- Use case IDs follow the UC-{3-digit} convention
- PlantUML syntax is valid (no missing
@enduml, proper arrow syntax)
- Each use case traces to at least one functional requirement in
Similar Skills
Stats
Parent Repo Stars37
Parent Repo Forks7
Last CommitFeb 23, 2026