use-case-specification
Creates a reusable use case specification file that defines the business problem, stakeholders, and measurable success criteria for model customization, as recommended by the AWS Responsible AI Lens. Use as the default first step in any model customization plan. Skip only if the user explicitly declines or already has a use case specification to reuse. Captures problem statement, primary users, and LLM-as-a-Judge success tenets.
Profile →npx skills add awslabs/agent-plugins --skill use-case-specification --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Use Case Specification Multi-turn conversation to gather use case details and produce a use case specification document. ## Principles 1. **One thing at a time.** Each response advances exactly one decision or collects one piece of information. 2. **Confirm before proceeding.** Wait for the user to approve the spec before considering this skill complete. 3. **Infer, don't interrogate.** Use what's already known from the conversation. Only ask when you truly can't infer. 4. **Do NOT ask about base model selection.** Model selection is handled exclusively by the model-selection skill. ## Workflow ### Step 0: Check for Existing Spec Before starting discovery, check if a `*_use_case_spec.md` file already exists in the project. If it does, present it to the user and ask whether they want to reuse it, modify it, or start fresh. ### Phase 1: Discovery (1–3 turns) Review what is already known from the conversation so far, then identify what is still missing. You need these three things: - **What** is the problem the user is trying to solve with model customization - **Who** will use the finetuned model and in what context - **Which** success criteria can be used to evaluate how well the
- Principles
- Workflow
- Step 0: Check for Existing Spec
- Phase 1: Discovery (1–3 turns)
- Phase 2: Producing a Use Case Specification Document
- usecasespecification Edit Protocol
What does the use-case-specification skill do?
Creates a reusable use case specification file that defines the business problem, stakeholders, and measurable success criteria for model customization, as recommended by the AWS Responsible AI Lens. Use as the default first step in any model customization plan. Skip only if the user explicitly declines or already has a use case specification to reuse. Captures problem statement, primary users, and LLM-as-a-Judge success tenets.
How do I install it?
Run `npx skills add awslabs/agent-plugins --skill use-case-specification --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From awslabs/agent-plugins, a repository with 850 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.