# TEMPLATE — references/usecases.md

Reference example: `skills/recruitment-consultant/references/usecases.md`
(gold standard — match its density and altitude).

## Purpose
Ranked work packages an AI agent with this skill can take over or support.
This is the file a buyer reads to decide whether the package is useful.

## Structure (exactly this)
```markdown
# Use cases — <occupation title>

Ranked work packages the agent can take over or support, highest leverage
first. Grounded in the O*NET task inventory (see tasks.md), the ESCO
competence profile (see skills.md) and market evidence (see market.md).

## 1. <Use case name, noun phrase>
<2-4 lines: what the agent does, concrete inputs, concrete output.>
Output: <the deliverable, one line>.

## 2. ...
```

## Fill rules
1. **6-8 use cases**, ranked by leverage: how much of the occupation's
   day-to-day (per responsibilities in market.md + tasks.md) does it cover,
   and how well can an LLM actually do it. Desk/document work ranks above
   physical work — for manual occupations, the agent's use cases are the
   *paperwork around the craft* (quoting, compliance docs, scheduling,
   customer communication), never the physical act itself.
2. Every use case must trace to at least one evidence anchor: an O*NET task,
   an ESCO skill, or a market.md responsibility with >= 10 % share. Cite
   market percentages inline where they strengthen the case
   ("appears in 52 % of ads").
3. Name concrete inputs and outputs. "Output:" line is mandatory —
   a deliverable a human can accept or reject.
4. English, imperative-lean prose, 2-4 lines per use case, no adjectival
   filler ("powerful", "seamless"), no capability claims beyond the evidence.
5. If a use case needs tools the occupation actually uses (ATS, CAD, POS),
   name the *category* plus the market-leading products from market.md.

## Do
- "Score applications against the intake scorecard, produce a shortlist with
  per-candidate rationale (evidence quotes from the CV, open questions,
  red flags to verify — never auto-reject)." — concrete, bounded, honest.
- Rank pipeline reporting above interview small talk: leverage order.

## Don't
- "Help with all recruiting tasks end-to-end" — unbounded, no deliverable.
- "Revolutionize your hiring workflow" — marketing filler.
- A use case for a surgeon template: "perform the operation" — physical act;
  correct would be "pre-op documentation and consent-form preparation".
- Inventing percentages or citing market.md numbers that are not in the file.
