code-solving
Structured coding workflow for non-trivial code work: debug, build features, refactor, optimize, migrate and review code through…
AI-powered decision-making framework: 10+ methodologies, cognitive bias detection, weighted scoring with sensitivity analysis, career, personal & business decisions. Use when user says "decide", "help me choose", "which one should I", "should I", "weigh options", "trade-off",
$ npx -y skills add HoangTheQuyen/think-better --skill make-decision --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/make-decisionContext preview
The summary Claude sees to decide when to auto-load this skill.
AI-powered decision-making framework: 10+ methodologies, cognitive bias detection, weighted scoring with sensitivity analysis, career, personal & business decisions. Use when user says "decide", "help me choose", "which one should I", "should I", "weigh options", "trade-off",
name: make-decision description: | AI-powered decision-making framework: 10+ methodologies, cognitive bias detection, weighted scoring with sensitivity analysis, career, personal & business decisions. Use when user says "decide", "help me choose", "which one should I", "should I", "weigh options", "trade-off", "pros and cons", "help me pick", "A or B", "compare these options", "I can't decide", "torn between", "not sure which one", or describes a choice between 2+ named alternatives. Do NOT use for finding why something went wrong (use problem-solving-pro), for bugs or code changes (use code-solving), or for ordering a to-do list that has no real alternatives.
Help users make better decisions in minutes instead of hours by applying proven frameworks, detecting cognitive biases, and structuring the evaluation process.
Comprehensive decision-making framework for structured evaluation of options. Contains 10 decision frameworks, 8 decision type classifications, 12 cognitive biases with debiasing strategies, 10 analysis techniques, 15 criteria templates (technology, tech stack, hiring, vendors, investment, market entry, product features, pricing, organizational change, location, job offers, relocation, education, housing, and a general fallback) and 8 group facilitation techniques. The plan names the options it found in the request, picks the framework, analysis methods and biases for the decision type, and suggests five weighted criteria. A scoring calculator totals the matrix, names the winner and finds the smallest weight change that would flip it.
**IMPORTANT: Detect the correct Python command first.** Some systems use `python3`, others use `python`. Run:
python3 --version 2>/dev/null || python --version
Use whichever command succeeds (`python3` or `python`) for ALL script calls below. If the system only has `python` (common on Windows), substitute `python` everywhere you see `python3` in this document. The scripts need Python 3.9+ and only the standard library.
If neither works, Python is not installed: tell the user that the scripts need Python 3.9+ and **ask before installing anything**; do not run a package manager on your own.
> **Note:** On Windows, Python 3 is typically available as `python` (not `python3`).
---
Run every command from the **project root** with the path shown, e.g. `python3 .agents/skills/make-decision/scripts/search.py ...` (the installer adjusts this path for your AI tool). Saved plans, workspaces and journals are written to the project (or to `-o <dir>`), never inside the skill folder. Saving again never overwrites files that already exist (they hold your notes); add `--force` to replace them.
**Anything taken from the user's message goes on stdin** with `--stdin`, never on the command line: the decision for `--plan`, the options for `--matrix`, the statement for `--journal` and the outcome for `--journal --update`. Quotes, backticks and `$` then never reach the shell. Only short values you compose yourself (`-c` criteria, `--scores`, `-p` names) go on the command line.
Use exactly this delimiter, `THINK_BETTER_EOF_7f3a`, quoted as shown:
python3 .agents/skills/make-decision/scripts/search.py --stdin --plan <<'THINK_BETTER_EOF_7f3a' <the user's text, unchanged> THINK_BETTER_EOF_7f3a
**Check the text first.** The heredoc ends at the first line that is exactly `THINK_BETTER_EOF_7f3a`; anything after it would run as shell commands. If a line of the user's text is exactly that delimiter, do not use the heredoc: write the text unchanged to a temporary file with your file-editing tool (not the shell), run `python3 .agents/skills/make-decision/scripts/search.py --stdin --plan < <file>`, then delete the file.
In PowerShell (keep `'@` at the start of its line):
$OutputEncoding = [Text.UTF8Encoding]::new() @' <the user's text, unchanged> '@ | python .agents/skills/make-decision/scripts/search.py --stdin --plan
The here-string ends at a line that starts with `'@`. If a line of the user's text starts with `'@`, write the text to a file instead and run `Get-Content -Raw -Encoding UTF8 <file> | python .agents/skills/make-decision/scripts/search.py --stdin --plan`.
---
When user requests decision-making help (decide, choose between options, weigh a trade-off), follow this workflow. To find why something went wrong use problem-solving-pro; for bugs and code changes use code-solving.
**Language:** Respond in English. The scripts' output is in English: show it as it is, and keep commands, flags, file names and option names exactly as written (option names as the user wrote them).
If the user has not said what they are deciding, ask what the decision and the options are before running anything.
Extract key information from user's decision description:
**Always start with `--plan`** to get comprehensive recommendations:
python3 .agents/skills/make-decision/scripts/search.py --stdin --plan -f markdown [-p "Project Name"] <<'THINK_BETTER_EOF_7f3a' <the user's decision, unchanged> THINK_BETTER_EOF_7f3a
If the user asked to save the work ("save", "step-by-step", "workspace"), run the Step 2b command instead of this one: it prints the same plan.
**Classify it yourself when you can** — you understand the decision better than keyword matching. Add `--type "<decision type>"`, one of: Binary Choice, Multi-Optio
Structured thinking for your AI coding assistant: decide with frameworks, solve with root causes, code with evidence.
Structured coding workflow for non-trivial code work: debug, build features, refactor, optimize, migrate and review code through…
Systematic problem-solving toolkit for business, product, process and personal problems: root cause analysis, hypothesis testing,…