Use ai-use-case-triage

Turn a pile of candidate AI use cases into a ranked portfolio

Turn a pile of candidate AI use cases into a ranked portfolio — each scored on value, feasibility, and risk with the weights shown, a recommended first slice that can prove or kill the thesis, and an explicit not-yet list with the condition that would promote each entry.

Reach for it when a team has more AI ideas than capacity and needs to choose, or asks "where should we actually start with AI". Do NOT use to assess whether the organisation is ready at all (that's ai-readiness-assessment) or to price a single decision (that's business-case).

Install it

npx skilldrop-cli install ai-use-case-triage                 # Claude Code, your user folder
npx skilldrop-cli install ai-use-case-triage --project       # Claude Code, this repo
npx skilldrop-cli install ai-use-case-triage --ide cursor    # or kiro, codex, antigravity, copilot

It is part of the AI engineering pack: --pack ai-engineering installs it with its neighbours.

Ask for it

Say it the way you would to a colleague. Requests like these route to it:

• "Which AI use cases should we do first?"
• "Rank these AI ideas by value and feasibility"
• "We have more AI ideas than capacity — help us choose"
• "Where should we actually start with AI?"

Requests like these belong to a different skill, so it shouldn't answer them:

• "Are we ready to adopt AI at all?"
• "Build the business case for this one investment"
• "Write the PRD for the feature we picked"

If another skill answers instead, ask for this one by name: "use ai-use-case-triage".

Check what you get

A good result:

• The weights are shown and justified in one line. A ranking with hidden weights is an opinion wearing a table.
• Every score has a one-line reason. A bare 4 is not a judgement anyone can challenge.
• The not-yet list is non-empty, and every entry carries a promotion condition. If nothing was rejected, the triage didn't happen.
• Each candidate names a workflow and a person, not a technology.
• The first slice has a kill condition with an observable and a time box.
• Unknown numbers are marked directional, never invented — a fabricated ROI figure poisons every decision downstream.

Use something else when

• Assessing whether the organisation can adopt anything yet — that's ai-readiness-assessment.
• Pricing one option properly (build vs buy, Option 0, cost layers) — that's business-case.
• Planning the human rollout of a chosen use case — that's ai-adoption-rollout.
• Writing requirements for the thing you picked — that's prd-draft.

Next

• SKILL.md, the instructions the agent reads
• Its page on the site
• Related: ai-adoption-rollout, ai-readiness-assessment, business-case, llm-eval-harness, prd-draft, success-metrics

Edit this page on GitHub · View source