Skip to content

mmaideveloper/aiarchitecttoolkit / skills/generate-use-case

generate-use-case

Verified

Create, refine, and review source-backed architecture use-case documents with actors, goals, flows, requirements, data handling, compliance controls, acceptance criteria, and stakeholder feedback. Use when the user supplies a use-case idea or reference such as UC-001, asks for a draft, or wants an existing use case updated after stakeholder discussion.

FileKindSize
SKILL.mdskill md3.1 KB
agents/openai.yamlconfig225 B
assets/use-case-template.mdmarkdown2.2 KB
references/use-case-quality.mdmarkdown671 B

assets/use-case-template.md

View on GitHub
# UC-<NNN>: <Outcome-oriented title>

## Record

- Status: Draft
- Owner: <owner or Unknown>
- Date: <YYYY-MM-DD>
- Stakeholders: <roles, not personal data>
- Related artifacts: <links or None>

## Goal and Business Outcome

<Why this use case exists and how success is measured.>

## Scope

### In scope

- <item>

### Out of scope

- <item>

## Actors and Responsibilities

| Actor or system | Responsibility | Evidence/confidence |
|---|---|---|
| <actor> | <responsibility> | <source and Confirmed/Assumption/To verify/Unknown> |

## Preconditions and Trigger

- Preconditions: <conditions>
- Trigger: <event>

## Main Success Flow

1. <observable interaction>

## Alternate and Failure Flows

| Condition | Expected behavior | Recovery or human escalation |
|---|---|---|
| <condition> | <behavior> | <action> |

## Information and Data

| Data category | Purpose | Source/recipient | Retention/deletion | Classification status |
|---|---|---|---|---|
| <category, no real records> | <purpose> | <flow> | <rule> | <Confirmed/To classify> |

## Requirements and Constraints

### Functional requirements

- `FR-<NN>`: <testable requirement>

### Quality attributes

- `QA-<NN>`: <security, privacy, safety, availability, interoperability, operability, or performance scenario>

## Privacy, AI, and Sector Governance Assessment

- Personal/special-category data: <None identified/description/To classify>
- Lawful basis or consent: <basis/To verify/Not applicable>
- Data minimization and purpose limitation: <controls>
- Retention, deletion, and subject rights: <controls>
- AI role and risk classification: <assessment/To classify>
- Transparency, traceability, and human oversight: <controls>
- Compliance blockers: <None or list>

## Acceptance Criteria

- [ ] <Given/when/then or other observable criterion>

## Assumptions and Open Questions

| Item | State | Owner/source | Due date |
|---|---|---|---|
| <item> | <Assumption/To verify/Unknown> | <owner/source> | <date or Unknown> |

## Evidence

| Claim | Source | Confidence |
|---|---|---|
| <claim> | <repository path, authorized URL, or meeting/ticket ID> | <Confirmed/etc.> |

## Stakeholder Feedback Log

| Date | Source/reviewer role | Change or outcome |
|---|---|---|
| <date> | <source> | <summary> |
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall