agentleFS
ysskrishnaysskrishna/ai-agent-skills/skills/tradeoff-analysis/SKILL.md

tradeoff-analysis

Skill20 starsChanged 29 days agoMITView on GitHub

Use for tradeoff analysis, or when the user must pick between concrete options: "A or B?", "which library should we use?", "build vs buy", "compare these approaches". Scores options on weighted criteria, tests sensitivity and reversibility. Skip for open ideation or single-option reviews.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Gather first: Read docs, benchmarks, pricing, the codebase and constraints before scoring.

    line 26

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Tradeoff Analysis

Choose among a small set of real options with the criteria, weights and evidence in plain view. A weighted decision matrix with a sensitivity check and a reversibility check.

When to use

  • Picking a library, vendor, architecture, plan, hire, design or build-vs-buy.
  • "A or B?", "compare these", "which should we pick", "is it worth it".
  • A decision the user must defend to others.

Skip: generating options from scratch (explore first, then come here), reviewing one plan for flaws, or ranking a long backlog.

Before you start

  1. State in one block: Decision (one sentence), Deadline or cost of delay, and Pass (Options, Must-haves, Criteria, Score, Sensitivity, Reversibility, Recommendation).
  2. Gather first. Read docs, benchmarks, pricing, the codebase and constraints before scoring. Every score needs a one-line basis; unsupported scores are marked [ESTIMATED]. Ask up to 3 questions only for goals and constraints tools cannot answer.
  3. Light path. Small ask: 2-3 options, 3 criteria, one-line reasons, a one-sentence sensitivity check.

Steps

1. Options

2-5 genuinely different options, including do nothing or keep current when it is real.

2. Must-haves

Hard constraints (budget cap, compliance, deadline). An option that fails one is out; do not score it.

3. Criteria and weights

3-7 criteria that reflect the goal and do not overlap (avoid counting the same thing twice, such as "speed" and "performance"). Give weights that sum to 100 and say why the top weight is highest.

4. Score

Rate each option per criterion from 1 (poor) to 5 (strong), with a short basis.

Criterion (weight)Option AOption B
... (40)4 - basis3 - basis
Weighted total

5. Sensitivity

Change the largest weight by about 10 points, or the least certain score by one. Does the winner change? Name the one criterion or score that flips the result.

6. Reversibility

How costly is it to undo this choice (switching cost, data lock-in, contract length, time)? Easy to reverse: decide faster and favor learning. Hard to reverse: spend more effort on evidence.

7. Recommendation

The pick, the main reason, the main cost you accept, and what would change the pick. For money or time tradeoffs, add a compact cost-benefit line: expected benefit range minus cost range, with the unit and period.

Pitfalls

  • False precision: a 3.8 vs 3.6 gap is a tie. Say so and decide on sensitivity and reversibility.
  • Weights chosen after seeing the scores. Set them before scoring.
  • Criteria that restate the favorite option ("uses our preferred language").
  • Scores from impressions with no basis. Mark them [ESTIMATED].
  • Ignoring the cost of changing course later.

Worked example: references/example.md.

Checklist

  • Decision and options stated; do-nothing considered
  • Must-haves screened before scoring
  • Criteria are independent; weights set with a reason
  • Every score has a basis or [ESTIMATED]
  • Sensitivity names what flips the result
  • Reversibility assessed
  • Recommendation names the accepted cost and what would change it

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.