All skills
use-case-modeling
FoundationJIT onlyanalysis-agent: use when actors, goals, preconditions, triggers, paths, guarantees, postconditions, or acceptance traces need modeling; skip when no use-case decision exists.
- Group
- Domain modeling
- Supported roles
- MainAnalysisTaskReview
- Source
- SKILL.md
Use when
Trigger signals that make this skill the right owner
- model use cases actors preconditions postconditions and success guarantees
Do not use when
Anti-triggers — as binding as the triggers above
- no task-local use case modeling decision is required
Required inputs
What must be supplied before this skill can decide anything
- current task contract
- selected primary Professional Skill
- task-local trigger evidence
Output contract
What this skill owes the next role
- bounded use-case model with actors and authority, trigger and preconditions, decision paths, state and side effects, termination guarantees, acceptance trace, unknowns, and residual owners
Escalation signals
When this skill must hand the decision back
- Weak use cases blur product behavior with implementation mechanics
Loaded by
This skill never owns a task. These professionals may pull it in as Layer 3.
Targeted references
Each reference carries its own load condition. None of them enter context by default.
| Reference | Load when | Do not load when | Required by |
|---|---|---|---|
| checklist.mddecision-checklist | actor goal preconditions alternates failures or postconditions remain incomplete | accepted use case defines every material exit and guarantee | Analysis |
| evidence-patterns.mdevidence-pattern | actor rule path or postcondition claims need current proof | current source tests contracts and owner artifacts prove each claim | Analysis |
| fully-dressed-template.mdtemplate | a formal actor precondition postcondition and exception use-case artifact is required | the task only needs partial actor or scenario analysis | Analysis |