agentleFS
cwhited26cwhited26/pocket-agent-starter-skills/skills/decisions/three-option-framing/SKILL.md

three-option-framing

Skill0 starsChanged 4 months agoMITView on GitHub

Frame a decision as three real options with their trade-offs, never a single take-it-or-leave-it recommendation. Any time the owner faces a real choice — a vendor, a price, a direction. When you'd otherwise just hand them one answer.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep it scannable: three options, the trade-off on each, your pick last.

    line 24

≈ “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

Always Three Options

One option is an order; three options is a decision. Give the owner three real paths with honest trade-offs so they're choosing, not just approving the one thing you put in front of them.

The technique

  • Build three genuine options, not one real choice padded with two strawmen. Each has to be something a reasonable person might pick.
  • Name the trade-off on each — what you give up to get what it offers. No option is free; show the cost.
  • Make them actually different: a cheap-and-fast, a safe-and-thorough, a bold-and-risky — not three shades of the same move.
  • Say which you'd pick and why, but after laying out all three — a recommendation, not a foregone conclusion.
  • Keep it scannable: three options, the trade-off on each, your pick last. The owner decides in a minute.

Do this, not that

Do: "Three ways to go on the hire: (A) contractor now — fast, flexible, costs more per hour. (B) part-timer — cheaper, slower to ramp, you manage them. (C) wait a quarter — no cost, but you stay the bottleneck. I'd do A — the bottleneck's costing more than the rate. Your call."

Don't: Hand back "You should hire a contractor" with no alternatives — so the owner either rubber-stamps it or has to go generate the options themselves to feel like they actually decided.

Why this works

A single recommendation puts the owner in a corner: agree or push back, with no map of the territory. Three real options with trade-offs hands them the map — they see what each path costs and choose with their eyes open. It also surfaces the option you might have missed, and it respects that it's their business and their call, not yours to make by omission.

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.