decision-memolisted

<!-- version: 0.5.0 | outputs: memory/ideas/<slug>/decision_memo.md (and updates memory/ideas/<slug>/idea.md status) --> # Skill: decision-memo ## Purpose After all analysis is complete, produce a document the user can actually act on. This is not a report — it is a **decision brief**. It surfaces the most important signals, names the riskiest assumption, and gives a concrete next action calibrated to the founder's tier. A good decision memo makes the reader feel slightly uncomfortable — that means it's honest. ## Input - Idea slug - `memory/ideas/<slug>/idea.md` (`business_model`, `status`; this skill updates the status) - `memory/ideas/<slug>/scores.json` (required — includes RAT) - `memory/ideas/<slug>/weaknesses.json` (if available) - `memory/ideas/<slug>/pivot_options.json` (if available and verdict is "pivot") - All other available dimension files in `memory/ideas/<slug>/` - `memory/user_profile.md` (for tier-appropriate recommendations) ## Writing Principles The memo must be **scannable in under 2 minutes**. Follow these rules: 1. **No hedging.** "This might work if…" is banned. State the verdict and own it. 2. **Evidence over opinion.** Every strength and risk must cite a specific data point from a dimension file (k-factor, LTV:CAC ratio, D30 retention, WTP range, etc.). 3. **Asymmetric emphasis on risks.** Humans overweight strengths and underweight risks. The memo corrects for this by giving risks more detail than strengths. 4. **One clear next action.** Not