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.

MITAuto-check passedDevelopment

Install Decide

skills CLI
$ npx skills add coreyhaines31/makerskills --skill decide -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install coreyhaines31/makerskills decide --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/coreyhaines31/makerskills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/decide .claude/skills/decide && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
decide
GitHub stars
851
Token cost
~1.9k tokens
SKILL.md length
856 words
Files
2 (incl. references)
Skills in repo
21
Repo updated
First seen
Licence
MIT

At a glance

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.

  • Works in 7 steps: Capture the decision → Triage the question set → Walk through → …
  • I need to make a decision about
  • SKILL.md covers Step 1 — Capture the decision, Step 2 — Triage the question set, Step 3 — Walk through and Step 4 — Reach a call, plus 6 more sections
  • Reaches 37signals.com

What it does

Decide is an agent skill from coreyhaines31/makerskills. 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…

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/questions.md`).

It sits in Development, covering Architecture decision records and Feature launches and release readiness. The repository describes itself as: AI agent skills for the personal operator's craft — decisions, research, second-brain, content rotation, scenario modeling, and meta-skills to author more. Works with Claude… The licence is MIT.

When your agent uses it

  • I need to make a decision about
  • Stuck on a decision
  • Deciding between
  • What should I do about. This is both the decision-making workflow AND the decision log — making the decision is the act of logging it

Example prompts

  • “what does saying yes displace?”
  • “/decide,”
  • “help me decide,”
  • “/decide”

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Capture the decision
  2. Triage the question set
  3. Walk through
  4. Reach a call
  5. Set the revisit
  6. Archive
  7. Surface

What it can do on your machine

Read from SKILL.md and the folder at commit cc31579. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • 37signals.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Decide loads about 1.9k tokens when it runs, and up to ~3.2k if it reads all its reference files. Until then it costs about 214 tokens; SKILL.md has 856 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~214
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from coreyhaines31/makerskills at commit cc31579, republished under its MIT licence (© coreyhaines31). 856 words, ~1,889 tokens.

Download SKILL.mdSave it as .claude/skills/decide/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
decide
description
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 decide," "should I [X]," "I need to make a decision about," "stuck on a decision," "deciding between," "go/no-go on," "what should I do about." This is both the decision-making workflow AND the decision log — making the decision is the act of logging it.
metadata.version
0.3.1

/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 doorQ14 (is there a wrong decision?), Q17 (knock-on effects), Q34 (principles bent)
Time pressureQ5 (why hesitating?), Q15 (different tomorrow?), Q22 (when do we have to decide?)
Multiple people involvedQ21 (someone else's practice rep?), Q27 (would another opinion help?), Q35 (multiple people deciding what one should?)
Lots of data / analysisQ19 (what missing info would change it?), Q26 (data vs gut?), Q9 deepened
Recurring decisionQ11 (last time?), Q23 (one-and-done or repeating?)
Customer-facingQ24 (anyone outside depending?), Q25 (customer vs us impact?)
Money decisionQ38 (in the end, is this about money?), Q36 (return on effort?), Q39 (what does yes displace?)
Big time / focus commitmentQ39 (opportunity cost), Q36 (return on effort?), Q20 (creates or eliminates work?)
Stuck / not decidingQ4 (why hasn't it been made already?), Q10 (what if we don't decide?), Q31 (do you even care?)

Cap at ~8 questions. More than that turns into analysis paralysis (which is itself one of the things this skill exists to prevent).

Tell the user which questions you picked and why, then proceed.

Step 3 — Walk through

Ask the questions one at a time, or in a tight cluster if the user wants to write fast. Capture their answers verbatim — don't paraphrase into corporate-speak.

For Q9 (first instinct), get the answer BEFORE diving into analysis. The point is to surface the gut call so we can later check if "analysis" was just rationalization.

Step 4 — Reach a call

Synthesize the answers into a decision. Options:

  • Decide now — answers point to a clear call
  • Decide smaller — break into 2–3 smaller decisions (Q7)
  • Wait — flag what info / time would change the answer (Q19, Q15)
  • Don't decide — the decision doesn't need to be made (Q1, Q10)
  • Wrong person — kick to the right decider (Q2, Q35)

State the call clearly. No hedging.

Step 5 — Set the revisit

Pick a revisit date based on when consequences would show up:

  • Decisions about tools/processes: 30 days
  • Decisions about strategy/positioning: 90 days
  • Decisions about hires/partnerships: 90–180 days
  • Decisions about products/launches: 30–60 days post-launch

Write what to look for on the revisit ("did MRR move? did the partner ship? do clients still ask for X?").

Show full SKILL.md (330 more words)Show less

Step 6 — Archive

Archives live in ${MAKERSKILLS_CONFIG:-$HOME/.config/makerskills}/decide/archive/ (create the directory if missing). Never write archives inside the skill's own folder — skill installs and upgrades re-sync from source and wipe anything saved there.

Migration: if this skill's folder contains an old references/decisions-archive/ with user entries, move those files into the archive directory before writing anything new.

Write to <archive dir>/<YYYY-MM-DD>-<slug>.md:

markdown
# Decision: <one-line>

**Date:** YYYY-MM-DD
**Decide by:** <date or "open">
**Reversibility:** easy / hard / one-way door
**Stakes:** low / medium / high

## Context
<1–3 sentences>

## Questions

### <Q3 phrasing>
<answer>

### <Q8 phrasing>
<answer>

(only questions actually applied — heading is the question text, not "Q3")

## Decision
**<the call, stated clearly>**

## Rationale
<2–3 sentences synthesizing the answers>

## Expected outcome
<what should be true if this was right, by <date>>

## Revisit
**<YYYY-MM-DD>** — <what to look for>

## Source
Questions adapted from [The 37signals Guide to Making Decisions](https://37signals.com/how-we-make-decisions)

Append to <archive dir>/INDEX.md (create if missing):

markdown
- 2026-06-16 — [<decision>](./<filename>.md) — **<call>** — <one-line rationale> — revisit 2026-09-16

Step 7 — Surface

Show the archive entry in chat. Tell the user the archive path. Offer:

  • "Want me to schedule a /loop reminder for the revisit date?" (would use the loop skill to fire at the right time)
  • "Push to Notion as a decision card?"
  • "Need a follow-up decision after this one?"

Future enhancements

  • Auto-create a calendar event or cron reminder for the revisit (via your agent's scheduler if it has one, e.g. compound-engineering:schedule in Claude Code; otherwise a calendar event)
  • Composable with business-brainstorm — brainstorm scores the idea on 9 dimensions; decide formalizes the go/no-go after
  • Grep past decisions for patterns ("show me decisions I made that were marked 'easy reverse' but didn't reverse")

Composes with

  • business-brainstorm — brainstorm → decide is a natural pipeline for "should I build X"
  • deep-research — when a decision is waiting on info (Q19), trigger research first
  • Memory — load feedback_*.md for principles that might be at play (Q34)
  • loop / compound-engineering:schedule — for revisit reminders

Notes on quality

  • Don't ask all 38. The point of triage is to skip questions that don't apply. Eight relevant questions > thirty-eight padded ones.
  • Don't soften the call. "Probably yes, lean toward, maybe should" wastes the skill. Pick.
  • The first instinct (Q9) is sacred. Always capture it before analysis. If the final call differs from the first instinct, the rationale needs to explain why — that's the whole point of the question.
  • Archive every decision, even small ones. The compounding value comes from being able to grep "what did I decide about pricing last year" — and that requires writing them down even when they feel obvious in the moment.

© coreyhaines31, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/decide of coreyhaines31/makerskills.

  • SKILL.md
  • references/questions.md

Open the folder on GitHubat commit cc31579

Compare with similar skills

Decide next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Decide compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Decide this skillcoreyhaines31/makerskills851—~1.9kAutomated safety check: PassMIT
Repo Genomeruvnet/metaharness696—~772Automated safety check: PassMIT
Schematicblader/schematic241—~2.2kAutomated safety check: PassMIT
Herdr Pre-Release Auditherdrdev/herdr43k—~289Automated safety check: PassApache-2.0
Happier Reviewhappier-dev/happier1.9k—~4.5kAutomated safety check: PassMIT
Megaphone ReleaseKuberwastaken/megaphone170—~1.3kAutomated safety check: PassMIT

Similar skills

  • Repo Genome

    ruvnet/metaharness

    7-section readiness scorecard for a LOCAL repo. An agent skill from ruvnet/metaharness.

    696 GitHub stars~772 tokensUpdated today
    Product & Project ManagementAuto-check passed
  • Schematic

    blader/schematic

    Reverse engineer a detailed product and technical specification document from a git branch's implementation.

    241 GitHub stars~2.2k tokensUpdated 7 mo ago
    Product & Project ManagementAuto-check passed
  • Audit herdr release readiness by comparing commits since the base release against next-release changelog and docs. Use when asked to run or apply the repo's…

    43k GitHub stars~289 tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Happier Review

    happier-dev/happier

    Conduct evidence-backed Happier code, plan-completeness, session, worktree, feature, commit, branch, PR, codebase, and release-readiness reviews with affected-corridor analysis, high-confidence…

    1.9k GitHub stars~4.5k tokensUpdated today
    DevelopmentAuto-check passed
  • Megaphone Release

    Kuberwastaken/megaphone

    Prepare, validate, publish, and verify Megaphone releases. An agent skill from Kuberwastaken/megaphone.

    170 GitHub stars~1.3k tokensUpdated 2 mo ago
    DevelopmentAuto-check passed
  • Create Release Checklist

    software-mansion/smelter

    Generate a GitHub release-checklist issue for a full (non-RC) release of the Smelter server and/or the TypeScript SDK.

    734 GitHub stars~1.9k tokensUpdated today
    DevelopmentAuto-check: notes

More from coreyhaines31/makerskills

All 21 skills in this repo
  • Business Brainstorm

    coreyhaines31/makerskills

    When you want to pressure-test a potential new business, product, or side project against the serial-founder filter.

    851 GitHub stars~1.7k tokensUpdated yesterday
    Auto-check passed
  • Company Brain

    coreyhaines31/makerskills

    Your team's shared, AI-ready knowledge base — people, companies, meetings, SOPs, and decisions structured so an agent can answer on your team's behalf.

    851 GitHub stars~4.9k tokensUpdated yesterday
    Auto-check passed
  • Company Cfo

    coreyhaines31/makerskills

    Monthly CFO workflow for a company or agency — pull raw data from bank + payment processor + payroll + expense management, categorize and reconcile, compute end-of-month cash via transaction-sum…

    851 GitHub stars~4k tokensUpdated yesterday
    Auto-check: notes
  • Ingest

    coreyhaines31/makerskills

    When you paste raw human input — a call transcript (Grain, Zoom, Granola, Fathom), a text or email from a client/partner/friend, a voice-memo dump, or meeting notes — and want it converted into…

    851 GitHub stars~1.8k tokensUpdated yesterday
    Auto-check passed
  • Maker Council

    coreyhaines31/makerskills

    When you want multiple expert perspectives on a founder/operator question — a simulated board of advisors (Jason Fried, Elon Musk, Jeff Bezos, Jensen Huang, Bob Iger, Paul Graham, Naval Ravikant…

    851 GitHub stars~2.9k tokensUpdated yesterday
    Auto-check passed
  • Paste

    coreyhaines31/makerskills

    When you want to clean and reformat content (usually from your terminal) for pasting into Slack, Notion, Twitter/X, LinkedIn, email, GitHub, or plain text.

    851 GitHub stars~2.3k tokensUpdated yesterday
    Auto-check: notes

Questions about Decide

What does Decide 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. Decide is an agent skill from coreyhaines31/makerskills. 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.

When should I use Decide?

Decide fits situations like: I need to make a decision about; stuck on a decision; deciding between; what should I do about. This is both the decision-making workflow AND the decision log — making the decision is the act of logging it.

How do I install Decide in Claude Code?

Run `npx skills add coreyhaines31/makerskills --skill decide -a claude-code`. Or copy the skill folder (skills/decide in coreyhaines31/makerskills) into .claude/skills/decide in your project. Claude Code loads it when a task matches its description.

How do I install Decide in Codex?

Run `npx skills add coreyhaines31/makerskills --skill decide -a codex`. Or copy the skill folder (skills/decide in coreyhaines31/makerskills) into .agents/skills/decide in your project. Codex loads it when a task matches its description.

Can I use Decide in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add coreyhaines31/makerskills --skill decide -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/decide, .gemini/skills/decide, .github/skills/decide and .opencode/skills/decide in your project.

What does Decide need to run?

SKILL.md names no scripts, command-line tools or credentials: Decide is instructions for the agent only.

Does Decide access the network?

SKILL.md names 1 domain. In commands or code: 37signals.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Decide safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Decide use?

Decide is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Decide use?

About 1.9k tokens (SKILL.md is roughly 7.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.3k tokens, read only when the agent opens those files.

What are the alternatives to Decide?

Skills that share tags, products or a category with Decide: Repo Genome (ruvnet/metaharness, 696 stars), Schematic (blader/schematic, 241 stars), Herdr Pre-Release Audit (herdrdev/herdr, 43k stars) and Happier Review (happier-dev/happier, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Decide?

coreyhaines31 (a GitHub user) maintains it in coreyhaines31/makerskills, which has 851 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 8, 2026.

Source: coreyhaines31/makerskills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.