Run a decision-driving meeting (pre-read + agenda + live capture)

Act as a sharp chief-of-staff who believes meetings exist to make decisions — everything else is a Slack message. We're meeting about [TOPIC] for [DURATION] with [ROLES/ATTENDEES]. Desired outcome: [WHAT MUST BE DECIDED].

Produce three things:

**1) PRE-READ PACKET** (to send 24 hours before — so the meeting can be decisions, not presentations):
- A 1-page brief: context summary (what happened, why we're here), the 1–3 specific decisions to be made (framed as yes/no or A-vs-B choices, not open-ended discussions), and the relevant data/analysis each attendee should review.
- For each decision, include: the recommended option (with a 2-sentence rationale), the key tradeoff, and the one question attendees should come prepared to answer.
- The pre-read must be readable in under 5 minutes. If it's longer, it won't get read.
- Include a note: 'If you have concerns about the recommendations, share them in [CHANNEL] before the meeting so we can address them live.'

**2) AGENDA** — time-boxed, designed to reach decisions, not discuss topics:
- Assign each agenda item a **RAPID role**: who is the **D**ecider (one person, final call), who provides **R**ecommendation, who must **A**gree (has veto), who gives **I**nput (consulted but no veto), and who **P**erforms (executes after).
- For each item: time allocation, the specific decision or output it must produce, who leads, and the RAPID roles. Front-load the highest-stakes decision while energy is high.
- Include a 3-minute 'decisions + owners' recap at the end — this is the most important part.
- Cut anything that's FYI or status-update — move it to async with a note about where it lives.
- If the desired outcome can't fit the duration, say so. Propose what to cut, what to defer, or what needs a pre-read decision (async approval before the meeting).

**3) LIVE-CAPTURE TEMPLATE** — a fill-in doc for during the meeting:

| Section | Format |
|---|---|
| Decisions Made | Decision — Rationale (1 line) — Decider — Date effective |
| Action Items | Task — Owner — Due date — How we'll know it's done |
| **Parking Lot** | Topic — Why it was parked — Owner to follow up — Deadline to revisit |
| Open Questions | Question — Who owns finding the answer — By when |
| Meeting Score | Quick 1–5: 'Did we decide what we came to decide?' |

**Parking lot protocol**: When a tangent emerges (and it will), the facilitator says: 'That's important but not what we're deciding today — I'm adding it to the parking lot with your name. You'll own scheduling a follow-up by [date].' This keeps the meeting on track without dismissing valid concerns.

Finally, write the **post-meeting Slack/Notion message** (copy-paste ready): a 3–5 line summary with decisions, owners, and deadlines. Anyone who wasn't in the meeting should understand what was decided in 30 seconds.