AI Unified Process core - stack-agnostic requirements, entity model, and use cases, plus the construction orchestrators for layer plugins
95%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Use Case ID: UC-XXX
Use Case Name: [Descriptive Name]
Primary Actor: [Role that pursues the goal — several comma-separated when each starts the use case alone and pursues the same goal]
Secondary Actors: [Supporting roles or external systems, comma-separated — omit this line when there are none]
Goal: [In one sentence: the observable outcome the actor achieves and why — not "use the system"]
Trigger: [The event that starts the use case — an actor's request, a point in time, or a message from an external system; not a state that is already true]
Status: Draft | Reviewed | Approved | Implemented | Tested | Done | Obsolete
Requirements: FR-XXX, NFR-XXX, C-XXX
Layers: [UI, API, or Service — the entry layers that offer this use case; omit this line when every entry layer of the project offers it]
Mockup: [Links to the mockups or wireframes of this use case — a Figma link, an image, or a Markdown sketch under docs/; omit this line when there is none]
API: [Links to the operations of the agreed API contract this use case is offered through — the contract file with the operationId or AsyncAPI channel as fragment; omit this line when there is none]
Trigger: [Condition that triggers this flow] (step N)
Flow:
[Description of the business rule that applies to this use case]
.tessl-plugin
skills
acceptance-protocol
references
business-process
entity-model
references
next
open-questions
references
release-notes
references
requirements
reverse-engineer
spec-review
stack
references
test-case
test-case-coverage
test-case-implement
use-case-coverage
use-case-diagram
references
use-case-implement
references
use-case-spec
use-case-test
references
user-guide