Menu

Individual skill

decision-maker

Compares multiple candidate solutions against explicit criteria and trade-offs, and produces a structured recommendation. Use when the user has several real options and needs a defensible pick, not just a pros/cons list.

skills/reasoning/decision-maker/SKILL.md

Read pinned source

Source commit d0a9928d24afb7df0fad2f2f35f65d3938a6926a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
27
Repository last updated
Aug 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

## Purpose

Given two or more candidate solutions to the same problem, evaluate them against explicit criteria and trade-offs, and produce one clear, defensible recommendation — not a noncommittal summary of pros and cons.

## When to Use

- The user has already narrowed a decision down to a shortlist of real options.
- A choice has real trade-offs and no option is a strict superset of the others.
- The user needs a documented rationale they can share with others (a design doc, an ADR).

## What to Analyze

1. **Confirm the options** being compared and the actual decision being made.
2. **Establish criteria** — ask for or infer the dimensions that matter (cost, latency, team familiarity, time to ship, long-term maintainability, reversibility). State them explicitly before scoring.