AI Use-Case Scorer
Turns "I should be using AI more" into "here are the 3 things I'm building this week, here's why, and here's what I'm explicitly NOT doing." Built for the individual IC trying to figure out where to deploy AI in their own work.
Why this exists
Most AI-use-case lists are theater — pages of "potential" use cases that never get built. This skill compresses the call: of the use cases on your list, which 2–3 actually pay off this month, and which to ignore.
Built for the IC. If you're rolling AI out to a 50-person team, this is the wrong framework — that's change management, not personal scoring.
Scoring framework: V × F × S
Each use case scored on three axes (1–5 scale).
Value — what's the upside?
Value score = round(avg of three sub-scores)
Feasibility — can you actually do it?
Feasibility score = round(avg of two sub-scores)
Safety — what could go wrong? (Inverted: higher = safer)
Safety score = round(avg of three sub-scores)
Final score = V × F × S
Range: 1 (don't bother) to 125 (perfect).
Tiers
- ≥ 60 → Do Now. This week.
- 30–59 → Do This Quarter. Plan it.
- 10–29 → Park. Revisit when tools mature or context changes.
- < 10 → Avoid. Effort or risk too high vs. payoff.
1. Scored table
2. Top 3 — Do Now
For each: 1-line description, 1-line why-now, 1-line first step (must be doable in <1 hour).
3. Park / Avoid (with the "what would have to change" trigger)
Often more useful than the Do Now list — tells you what you're explicitly NOT building, and when to revisit.
Process
Brainstorm if needed. If user gives a workflow instead of a list, walk through their week — every recurring task, every painful task, every "I keep meaning to..." task. Aim for 8–12 candidates.
Score each on V/F/S. Use the rubric. Push back on 5s — they should be rare.
Compute scores + assign tiers.
Write the top 3 tightly. First step must be doable in under 1 hour. If it isn't, the score was wrong.
Flag the parked + avoided. With the trigger condition for revisiting.