use-case-modeling
Use Case Modeling
Overview
Use this skill to make behavior explicit across actors and system boundaries before coding.
Scope Boundaries
- Approved requirements still leave interaction behavior unclear.
- Teams need aligned understanding of success, alternate, and failure flows.
- Boundary responsibilities across systems or roles are disputed.
Templates And Assets
- Use case specification template:
assets/use-case-template.md
Inputs To Gather
- Approved requirement set and known constraints.
- Actor definitions, permissions, and system boundaries.
- Business rules, integration dependencies, and error-handling expectations.
Deliverables
- Use case set with preconditions, triggers, outcomes, and postconditions.
- Main, alternate, and exception flow definitions.
- Requirement-gap list mapped to unresolved use-case steps.
Workflow
- Identify actors and goals with clear boundary ownership.
- Define main success flow from trigger to postcondition.
- Add alternate flows for expected variation (authorization differences, optional paths, retries).
- Add exception flows for failure and recovery behavior.
- Validate data/state transitions and side effects at each step.
- Trace uncovered ambiguity back to requirement items for refinement.
Quality Standard
- Every critical actor goal has an explicit end-to-end flow.
- Exception behavior is concrete, not implied by generic error text.
- Boundary handoffs specify who validates, who mutates, and who observes.
- Gaps are actionable and linked to requirement refinement tasks.
Failure Conditions
- Stop when system boundaries are not defined.
- Stop when exception handling cannot be mapped to responsible components.
- Escalate when unresolved use-case gaps block implementation planning.
More from kentoshimizu/sw-agent-skills
graph-algorithms
Graph algorithm workflow for modeling entities/relations and selecting traversal, path, ordering, or flow strategies. Use when correctness or performance depends on graph representation and algorithm choice; do not use for schema-only modeling or deployment topology planning.
14bash-style-guide
Style, review, and refactoring standards for Bash shell scripting. Trigger when `.sh` files, files with `#!/usr/bin/env bash` or `#!/bin/bash`, or CI workflow blocks with `shell: bash` are created, modified, or reviewed and Bash-specific quality controls (quoting safety, error handling, portability, readability) must be enforced. Do not use for generic POSIX `sh`, PowerShell, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
11architecture-clean-architecture
Clean Architecture workflow for enforcing dependency direction, stable domain boundaries, and use-case-centered application design. Use when teams must separate business rules from frameworks and delivery mechanisms; do not use for isolated module cleanup without boundary implications.
11powershell-style-guide
Style, review, and refactoring standards for PowerShell scripting. Trigger when `.ps1`, `.psm1`, `.psd1` files, or CI workflow blocks with `shell: pwsh` or `shell: powershell` are created, modified, or reviewed and PowerShell-specific quality controls (error handling, parameter validation, readability, operational safety) must be enforced. Do not use for Bash, generic POSIX `sh`, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
10github-codeowners-management
Govern CODEOWNERS rules so review routing reflects real ownership and risk boundaries on GitHub. Use when repository ownership mapping or mandatory reviewer rules must be defined, updated, or audited; do not use for non-GitHub runtime architecture or data-layer design.
9security-authentication
Security workflow for authentication architecture, credential lifecycle, and session/token assurance. Use when login, identity proofing, MFA, or session security decisions are required; do not use for authorization policy design or non-security quality tuning.
9