plugins/executive/skills/decision-frameworks/SKILL.md
Use when choosing between mutually exclusive strategic paths or building a repeatable decision process—constructs Decision Matrices with probability estimates and runs Pre-Mortems.
npx skillsauth add joellewis/skill-library decision-frameworksInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Decision frameworks provide the structural rigor to make high-quality choices under uncertainty. This skill transforms decision-making from an emotional "gut feel" into a probabilistic process by decoupling outcomes from process, identifying cognitive biases, and utilizing a latticework of mental models to uncover second-order consequences.
Every decision is a bet on a specific future. Shift from binary "Right/Wrong" thinking to probabilistic "Confidence" thinking. Acknowledging uncertainty (e.g., "I am 70% confident") improves decision quality and reduces the sting of bad outcomes.
Do not judge a decision solely by its outcome. A "good" result can come from a "bad" process due to luck. Evaluate the process used at the time of the decision, not the final result.
You cannot make wise decisions with a single mental model. You must have a "latticework" of models from multiple disciplines (math, physics, biology, psychology) to avoid the "Man with a Hammer" syndrome.
Know the boundaries of your knowledge. Decisions made outside your circle of competence have a much higher risk of failure. If you must decide outside your circle, seek a partner with the missing expertise.
When faced with multiple interpretations of a situation, choose the one that is most useful for making progress, even if it is not "100% true." Belief is a tool for action.
Clearly state the choice being made and the desired outcome.
Map the possibilities and probabilities. (Source: Duke, How to Decide)
Use the latticework to uncover hidden flaws. (Source: Munger, Parrish)
Imagine the decision has failed 12 months from now. (Source: Duke, How to Decide)
Record the reasoning at the time to prevent hindsight bias. (Source: Duke, Thinking in Bets)
A structured table mapping:
"Never attribute to malice that which is adequately explained by stupidity (or incompetence)." Use this to prevent emotional bias in interpersonal or competitive decisions.
The model (the map) is not the reality (the territory). Always check if the "map" you are using for a decision matches the actual "territory" on the ground.
devils-advocate — To stress-test the preferred option in the matrix.assumption-audit — To validate the probabilities assigned in Step 2.mental-model-library — For a broader set of models beyond the core three.databases
Use when a deliverable needs structured stakeholder sign-off before finalization—runs the pre-read, feedback-type alignment, and conflict-resolution protocol.
development
Use when you need to map who has power, who will be affected, and what motivates each party — produces a stakeholder map as an analytical artifact. This skill identifies and categorizes stakeholders; it does not persuade or influence them (use influence-architect for that).
testing
Use when beginning analytical or strategic tasks, facing undefined problems, or facing analysis paralysis—requires explicit problem definition before proceeding.
testing
Use when translating a product vision into engineering requirements—enforces the Working Backwards PR/FAQ method, requiring a customer-facing press release before any technical spec.