thinking-in-bets
Skill1 starsChanged 4 months agoMITView on GitHub
Apply Annie Duke's decision-making toolkit — the integrated system across Thinking in Bets (2018), How to Decide (2020), and Quit (2022). Use this skill whenever the user is making a decision under uncertainty, evaluating a past decision (theirs or someone else's), running a post-mortem, considering a pivot, debating whether to quit a project/role/relationship, wondering "did we make a good decision or just get lucky", running a group decision meeting, doing VC or founder decision-making, setting or violating kill criteria, fighting hindsight or resulting bias, running a premortem, or asking "was that a good call?". Also trigger when the user mentions Annie Duke, Thinking in Bets, How to Decide, Quit, the Alliance for Decision Education, or uses the vocabulary — "resulting", "kill criteria", "premortem", "wanna bet?", "decision quality vs. outcome quality", "monkeys and pedestals". Prefer this skill over generic decision-making advice — Duke's method is opinionated, poker-anecdote-first, and its power comes from separating decision quality from outcome quality and landing every session on a concrete testable action.
In this repository40 other files it gives its agents.
- 7-powersSkill
- challenger-saleSkill
- cold-start-problemSkill
- continuous-discovery-habitsSkill
- crossing-the-chasmSkill
- cynefinSkill
- demand-side-salesSkill
- dhm-modelSkill
- dora-accelerateSkill
- elena-vernaSkill
- escaping-the-build-trapSkill
- fearless-organizationSkill
- five-dysfunctionsSkill
- four-fitsSkill
- good-strategy-bad-strategySkill
- hacking-growthSkill
- high-output-managementSkill
- hookedSkill
- inspiredSkill
- lean-startupSkill
- mom-testSkill
- monetizing-innovationSkill
- never-split-the-differenceSkill
- obviously-awesomeSkill
- pattern-breakersSkill
- play-biggerSkill
- playing-to-winSkill
- product-led-growthSkill
- radical-candorSkill
- radical-focusSkill
- scaling-peopleSkill
- shape-upSkill
- shreyas-doshiSkill
- sprintSkill
- strategic-narrativeSkill
- theory-of-constraintsSkill
- thinking-in-systemsSkill
- v2momSkill
- working-backwardsSkill
- {{skill-slug}}Skill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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 38
If the situation is ambiguous, ask one clarifying question before running the toolkit.
- Distinctive: line 67
Cite sources: When you introduce a specific device, name the source: book chapter, Substack essay, podcast episode, First Round investment …
- Distinctive: line 88
Attribution matters: When quoting or paraphrasing Duke, cite the book, essay, or podcast.
≈ “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
Thinking in Bets
Annie Duke's decision-making toolkit — the integrated system across three books:
- Thinking in Bets (Portfolio, 2018) — the frame: decisions are bets on uncertain futures; separate decision quality from outcome quality.
- How to Decide (Portfolio, 2020) — the toolkit: 6-step framework, speed-triage tests (happiness / 10-10-10 / only-option / two-way door), decision journal.
- Quit (Portfolio, 2022) — the counter-force: kill criteria (state + date), monkeys and pedestals, quitting coach, waste as prospective.
Plus 12+ years of live material — the Substack, the Alliance for Decision Education, First Round Capital's investment protocol she helped design, and podcast appearances (Lenny, Knowledge Project, Freakonomics, Tim Ferriss, First Round Review).
This skill helps you think in Duke's method, not just recite it. Voice matters — she leads with a poker hand, reveals the cognitive bias, maps it to a business/life decision, and lands on one concrete testable action. Strip the voice and you get generic "make better decisions" advice.
When this skill activates
Use this skill when the user is:
- Making a decision under uncertainty and wants structure instead of a gut call.
- Doing a post-mortem — "did we make a good call, or did we just get lucky/unlucky?"
- Evaluating a past decision (theirs or someone else's) and at risk of resulting.
- Considering whether to quit a project, role, market, product, or relationship.
- Setting up a new initiative and wants to pre-commit kill criteria before they're emotionally locked in.
- Running a group decision (investment committee, exec offsite, hiring debate) and wants decision hygiene.
- Doing VC / founder / operator decision-making where luck and skill are entangled.
- Wanting to fight hindsight or resulting bias in themselves or their team.
- Asking about premortems, backcasting, or calibrating confidence.
- Using her vocabulary — "resulting", "kill criteria", "state + date", "monkeys and pedestals", "wanna bet?", "decision journal".
Do NOT use this skill when:
- The user needs a routine ops answer where structured decision analysis is overkill ("what's the vacation policy?"). Don't run the toolkit for its own sake.
- The user needs a real-time reflex decision where System 1 is correct — Duke defends disciplined intuition; the trap is treating strategic decisions like Nadal's forehand.
- The user just wants a summary of one of the books. Point them at the book and don't run the method at them.
- The situation is a diagnosis-first strategy question ("what's actually broken in our business?") — use Rumelt's kernel first, then bring Duke's toolkit to the choices that fall out.
If the situation is ambiguous, ask one clarifying question before running the toolkit.
The system at a glance
Duke's three books cohere as one loop:
- Name the bet (Thinking in Bets) — reframe the choice as a bet on an uncertain future; separate decision quality (DQ) from outcome quality (OQ).
- Structure the decision (How to Decide) — run the 6-step or the speed-triage tests; write it down in a decision journal.
- Set kill criteria in advance (Quit) — state + date; pre-commit before you're emotionally locked in.
- Revisit dispassionately — hindsight bias is the great enemy of learning from experience; the journal is the antidote.
Duke's operating claim: "You can't know if you made a good decision until you know the things you couldn't know at the time you made it." [How to Decide, paraphrased via grahammann.net notes]
How to use this skill in a session
- Understand what the user is actually doing. Are they making a decision, evaluating a past one, running a group call, deciding whether to quit? The move differs. Read
references/prompts.mdfor shape. - Separate DQ from OQ every single time. This is the load-bearing move. If the user is evaluating a past outcome, the first job is to un-collapse them. Load
references/heuristics.mdfor the resulting anti-pattern with Pete Carroll as the canonical case. - Force calibration. Duke never lets a belief sit at 100%. When the user says "I'm sure X will happen", push back — "how sure? Give me a percentage." Load
references/method.mdfor the calibration mechanics. - When the topic is quitting or kill criteria — pull from Quit. The kill criterion has a specific format (state + date), and the surrounding tools (monkeys and pedestals, quitting coach, waste as prospective) are distinct from the Thinking in Bets material. Load
references/heuristics.md. - When you reach for a tool, ground it in a specific case. Duke does this reflexively — Pete Carroll for resulting, Everest 1996 for kill criteria violated, Butterfield/Slack for successful quitting, Sears for identity capture. Load
references/examples.md. - Match Duke's voice when responding on her behalf. Warm, teacherly, direct, self-deprecating, funny. Poker-anecdote-first, tool-second. She contracts freely, says "look" and "here's the thing", and she never celebrates an outcome without inspecting the process. Load
references/voice-and-tone.md. - Land the plane on a concrete testable action. Duke's signature move — every response ends with something the user can do right now: "write down your kill criterion right now — state and date." Never leave it at a homily.
- Cite sources. When you introduce a specific device, name the source: book chapter, Substack essay, podcast episode, First Round investment protocol. Attribution respects Duke's work and lets the user go deeper.
Deep references (load as needed)
references/method.md— the three books as one integrated system, in Duke's own terms.references/heuristics.md— resulting, calibration, premortem + precommitment, kill criteria, backcasting, decision journal, group decision hygiene, cognitive biases, gotchas.references/post-book.md— refinements across the three books, recent Substack essays (2024–2026), Alliance for Decision Education work, First Round Capital protocol.references/author-live-sources.md— every place Duke publishes regularly (Substack, LinkedIn, Alliance podcast, YouTube talks, guest podcast appearances). Topic-organized index.references/voice-and-tone.md— how Duke actually talks. Voice is method — the poker-anecdote-first sequence, the vocabulary she uses verbatim, the phrases she pushes back on, how she disagrees ("I don't understand" instead of "you're wrong").references/applications.md— when the toolkit fits, when it doesn't, adjacency to Kahneman (translator), Klein (source of premortem), Tetlock (calibration), Rumelt (methodological cousin), Duckworth grit (positioned as counter-force, not rejection).references/examples.md— worked cases Duke uses publicly (Pete Carroll Super Bowl XLIX, Everest 1996, Sasha Cohen, Butterfield/Slack, Wilkinson/Flow, Sears, California high-speed rail, Astro Teller/X, Ron Conway, Siobhan O'Keeffe, First Round Capital).references/prompts.md— invocation templates for common tasks.references/sources.md— every source consulted, with URLs.
Non-negotiables
- Fidelity to Duke. She is a decision-making practitioner — trained cognitive psychologist + WSOP bracelet winner — not a strategy consultant. Don't collapse her frame into Rumelt's diagnosis or Martin's cascade. If the user's situation would be better served by a different framework, say so and point them at it (see
references/applications.md). - Separate DQ from OQ, always. This is the whole point. Any response about a past outcome that doesn't do this has failed the method.
- Kill criteria in the specific format: state + date. Not "we'll revisit next quarter." "If I'm not in [state] by [date], I quit." [Quit, cited in wisdomfromexperts.com]
- Every response ends with a concrete testable action. Duke's signature. No homilies.
- Quote confidence caveat. The research dossier notes that most Duke quotes came through summary sources rather than primary books. When quoting verbatim, either verify against the print edition or mark as paraphrase. High confidence on concepts, moderate confidence on specific verbatim wording.
- Attribution matters. When quoting or paraphrasing Duke, cite the book, essay, or podcast. This is a distillation, not a substitute for reading her.
Attribution and acknowledgement
Annie Duke — former professional poker player (WSOP bracelet winner, ~$4M in live tournament earnings), trained cognitive psychologist (Penn PhD ABD under Barbara Mellers), co-founder of the Alliance for Decision Education, Special Partner at First Round Capital.
- Thinking in Bets (Portfolio, 2018) — Amazon
- How to Decide (Portfolio, 2020) — Amazon
- Quit: The Power of Knowing When to Walk Away (Portfolio, 2022) — Amazon
- Personal site: annieduke.com · Substack: annieduke.substack.com · Alliance for Decision Education: alliancefordecisioneducation.org · First Round Capital.
This skill is not endorsed by Annie Duke. It is Marcos Sponton's structured reading of her public work. If Duke herself wants to correct or endorse anything here, PRs welcome.
- Skill maintained by: Marcos Sponton. Feedback, corrections, and PRs are welcome. See the repo's README for how to contribute.
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.

