decide

# /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?), Q17 (knock-on effects), Q34 (principles bent) | | Time pressure | Q5 (why hesitating?), Q15 (different tomorrow?), Q22 (when do we have to decide?) | | Multiple people involved | Q21 (someone else's practice rep?), Q27 (would another opinion help?), Q35 (multiple people deciding what one sho...