kill-or-double-downlisted

# Kill or Double Down ## When you activate - Quarterly (every 90 days) - User says: "portfolio review", "what should I kill?", "where to double-down?" - Run by `/kill-or-keep` skill ## What you produce Saved to `brain/decision-log/portfolio-review-YYYY-QN.md`: ``` ## Portfolio Review — <Q-YYYY> ### Snapshot | Product | Stage | MRR | Trend | Founder hours/wk | Verdict | |---|---|---|---|---|---| | linkedup | mvp | $0 | flat | 2 | <verdict> | | ventbox | launch | $200 | +20% | 4 | <verdict> | Verdict legend: **DOUBLE-DOWN** | **MAINTAIN** | **MINIMAL** | **KILL** ### DOUBLE-DOWN (allocate the most hours next quarter) - **<product>**: <why> — proposed quarterly target: <specific metric> - Top 3 initiatives: 1. ... 2. ... 3. ... ### MAINTAIN (steady hand, no major investment) - **<product>**: keep shipping, monitor metrics, no new feature work - Top recurring tasks: <list> ### MINIMAL (life support — < 2 hours/week) - **<product>**: keep alive, do not invest, revisit in 3 months - Why not killed: <reason — e.g. SEO compounding, low maintenance> ### KILL (sunset) - **<product>**: <reason — usually: no PMF after N months, no clear path> - Sunset plan: 1. Email users (T+0): announce, give 60 days 2. Disable signups (T+0) 3. Export data for any paying customer (T+30) 4. Shut down (T+60) 5. Archive code (T+60) 6. Write learnings to `brain/decision-log/postmortem-<product>-YYYY-MM-DD.md` ### Portfolio-level decisions 1. <decision —