CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

ai-unified-process/aiup-core

AI Unified Process core - stack-agnostic requirements, entity model, and use cases, plus the construction orchestrators for layer plugins

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

use-case.mdskills/use-case-spec/references/

Use Case: [Use Case Name]

Overview

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]

Preconditions

  • [Condition that must be true before the use case starts]

Main Success Scenario

  1. [Actor action or system response]
  2. [Next step]
  3. [Continue until goal is achieved]

Alternative Flows

A1: [Alternative Flow Name]

Trigger: [Condition that triggers this flow] (step N)
Flow:

  1. [Step that diverges from main flow]
  2. [Continuation]
  3. Use case continues at step N. (or: Use case ends.)

Postconditions

Success Postconditions

  • [State of the system after successful completion]

Failure Postconditions

  • [Minimum guarantee that holds for every unsuccessful end of the use case, e.g. no partial data is stored]

Business Rules

BR-XXX: [Rule Name]

[Description of the business rule that applies to this use case]

skills

README.md

tile.json