decide
When you have a decision to make and want a structured workflow that picks the load-bearing questions, walks through them, reaches a call (or "wait"), and archives the rationale for future reference. Based on the 37signals Guide to Making Decisions (38 questions) plus house additions like Q39 opportunity cost ("what does saying yes displace?"). Triages to 6–8 relevant questions per decision instead of forcing the full set. Archives every decision to ~/.config/makerskills/decide/archive/ with a revisit date so you can check later whether the call was right. Triggers on "/decide," "help me decid
npx skills add coreyhaines31/makerskills --skill decide --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# /decide — Structured decision workflow + archive Picks load-bearing questions from the 37signals guide, walks through them, reaches a call, archives the rationale with a revisit date. ## Step 1 — Capture the decision Get from the user: - **The decision** in one sentence (what are we deciding between?) - **Stakes**: low / medium / high (how much does this matter?) - **Reversibility**: easy / hard / one-way door - **Deadline**: when does this need to be decided? Or "open"? - **Context** (optional, 1–3 sentences) If any are missing, ask. Don't proceed with vague framing. ## Step 2 — Triage the question set Read `references/questions.md` for the full set (the 37signals 38 + house additions, e.g. Q39 opportunity cost) and category mapping. Pick 6–8 based on the decision's characteristics: **Default 5 (always ask):** - Q1 — Does this decision actually need to be made? - Q2 — Is the right person making this decision? - Q8 — How easily can we reverse it? - Q9 — First instinct? (capture before "thinking" muddies it) - Q3 — A year from now, how will we feel about this? **Add based on type:** | If… | Add | |---|---| | Reversibility = hard / one-way door | Q14 (is there a wrong decision?), Q
- Step 1 — Capture the decision
- Step 2 — Triage the question set
- Step 3 — Walk through
- Step 4 — Reach a call
- Step 5 — Set the revisit
- Step 6 — Archive
- Step 7 — Surface
- Future enhancements
- Composes with
- Notes on quality
What does the decide skill do?
When you have a decision to make and want a structured workflow that picks the load-bearing questions, walks through them, reaches a call (or "wait"), and archives the rationale for future reference. Based on the 37signals Guide to Making Decisions (38 questions) plus house additions like Q39 opportunity cost ("what does saying yes displace?"). Triages to 6–8 relevant questions per decision instead of forcing the full set. Archives every decision to ~/.config/makerskills/decide/archive/ with a revisit date so you can check later whether the call was right. Triggers on "/decide," "help me decid
How do I install it?
Run `npx skills add coreyhaines31/makerskills --skill decide --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From coreyhaines31/makerskills, a repository with 500 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.