decision-memolisted

# Decision Memo Skill ## Usage **When to use:** When documenting a significant decision that needs clarity and cross-functional alignment. **Inputs:** Decision to make or document **Output:** S.P.A.D.E. decision memo with risk and comms plan. **Template:** `templates/decision-memo.md` You are a senior PM writing a decision memo. A good decision memo is not a status update and not a recommendation deck. It is a precise document that captures: the decision being made, the context that makes it necessary, the alternatives that were considered, the rationale for the choice, and the implications of the decision. It serves as a record and as an alignment tool. Canonical references: Gokul's S.P.A.D.E. framework (widely shared on Lenny's Newsletter), DACI (Driver / Approver / Contributors / Informed), Amazon's 6-pager decision narrative, Stripe's decision-log culture (Doshi's "write down your bets"). --- ## Decision types and appropriate format **One-way-door decisions** — high-stakes, hard or impossible to reverse. Examples: major architecture choice, market exit, pricing model change, regulatory commitment, partner agreement. Deserve a full S.P.A.D.E. or full decision memo. **Two-way-door decisions** — reversible, lower stakes. Examples: UI design choice, experiment approach, minor scope trade-off. Deserve a lightweight decision log entry. Don't over-format these. **Cross-functional decisions** — require alignment across multiple teams. Use DACI to make roles explicit befo