decision-deliberation
Skill0 starsChanged 48 days agoMITView on GitHub
Prepare a consequential decision under uncertainty by running five functional lenses (incentives, system boundaries, historical patterns, second-order effects, cognitive bias), mapping unresolved tensions, and ending in options for the person who decides. Use when choosing among options, or before any exist; use Red Team Review when one chosen plan needs pressure-testing.
In this repository10 other files it gives its agents.
- brief-to-work-orderSkill
- eval-viability-checkSkill
- evidence-checkSkill
- grounded-researchSkill
- handoffSkill
- nutshellSkill
- red-team-reviewSkill
- retrievable-writingSkill
- skill-or-notSkill
- source-briefSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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
- Distinctive: line 42
Every pass runs all five. Each is a function, not a persona.
- Distinctive: line 56
Add a named voice (a specific thinker or tradition) only when it contributes a constraint the five lenses do not, stated in one sentence.
≈ “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.
Files
Decision Deliberation
Purpose
Prepare judgment under uncertainty. The skill does not make the decision. It makes the decision space harder to fake: assumptions surface, incentives are named, dissent stays visible, and the output ends in options the decision owner can act on.
When to use
- A strategic, business, architecture, hiring, or governance choice where evidence is partial or values are in tension.
- A decision with delayed or indirect consequences.
- A situation where the most elegant story may not be the truest one.
When not to use
- One chosen plan or draft already exists and needs pressure-testing. Use Red Team Review. Comparing two or more candidate plans still belongs here.
- Factual lookups, routine summaries, quick drafting, or anything where speed matters more than judgment quality.
- Licensed medical, legal, financial, or safety-critical advice, except as exploratory framing before qualified review.
Role boundary
Surface assumptions, pressure incentives, test boundaries, preserve dissent, map tensions, and turn deliberation into options, questions, or a decision record. Never decide for the owner, flatten disagreement into consensus, cover weak evidence with confident prose, or add ceremony that does not improve the decision.
The five lenses
Every pass runs all five. Each is a function, not a persona.
- Incentives. Who benefits, who is exposed, what incentives change on this path, and who could exploit it?
- System boundaries. What is inside the system, what is outside, what sits at the edge, and what breaks if the line is drawn wrong?
- Historical patterns. What analogues and base rates apply, where did similar efforts fail, and what is different enough to matter this time?
- Second-order effects. What adapts in response, what becomes easier or harder later, and which consequences are delayed or indirect?
- Cognitive bias. What motivated reasoning, anchor, or satisfying story may be crowding out evidence, and what missing evidence would change the view?
Add a named voice (a specific thinker or tradition) only when it contributes a constraint the five lenses do not, stated in one sentence. Default to none; use at most two; never for prestige or tone. Record its reason and whether it surfaced a distinction the lenses missed; if not, drop its findings.
Workflow
- Orient. State the question, stakes, time horizon, decision owner, evidence available, evidence missing, and what useful output looks like. If the question does not warrant deliberation, say so and stop.
- Run the lenses. For each: one to three findings, one risk or blind spot, and one question that would improve the decision. Pressure, not volume.
- Map tensions. Classify each real tension as action-blocking, decision-relevant, or watch-only. Do not resolve a tension to make the output cleaner.
- State refusals and limits. For example: the evidence cannot separate two explanations, the frame hides a value choice, or the question needs qualified medical, legal, or financial review.
- Check judgment. Separate what is clear, what is plausible but unproven, what is unresolved, what evidence would change the view, and what the owner must decide.
- Hand off. Options, next questions, and risks to monitor. Recommend only when the evidence supports it.
Failure modes
- Prestige theater: impressive names, generic output. Rerun with the lenses only.
- Premature coherence: an elegant conclusion with no dissent. Keep at least one unresolved question in the tension map.
- Aesthetic seduction: it sounds profound but changes nothing. Cut any line that does not clarify evidence, tension, refusal, or action.
- Responsibility drift: the output reads as the decision. Make the owner's choice explicit in the judgment check.
Output shape
# Decision Deliberation: [Question]
## Orientation
- Question:
- Stakes:
- Horizon:
- Decision owner:
- Evidence available:
- Evidence missing:
- Useful output:
## Lenses
### Incentives
- Finding:
- Risk:
- Better question:
### System boundaries
[same three lines]
### Historical patterns
[same three lines]
### Second-order effects
[same three lines]
### Cognitive bias
[same three lines]
## Named voices
- [Voice]: [one-sentence reason]. Surfaced a distinction the lenses missed: yes / no
[Or: None used. The five lenses were sufficient.]
## Tension map
- Action-blocking:
- Decision-relevant:
- Watch-only:
## Refusals and limits
- [What the evidence or frame cannot support]
## Judgment check
- Clear:
- Plausible but unproven:
- Unresolved:
- Evidence that would change the view:
- The owner must decide:
## Handoff
- Options:
- Next questions:
- Risks to monitor:
- Recommendation: [only if the evidence supports one]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
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.

