Meeting War Room Skill
Turn any transcript into decisions, owned actions with due dates and a recap to send.
GetKits 제작
차이를 직접 확인하세요
The fake decision it caught
사용 전
Wed Oct 7, Zoom transcript: [02:30] Priya: ok so let's do it. Beta goes to those 20 accounts on Tuesday. [04:40] Marco: I think we're all aligned on killing the CSV import, right? [04:44] Dana: yeah makes sense [04:46] Speaker 3: hmm, Acme uses it every Monday for their roster upload
사용 후
D1. Onboarding v2 beta goes to the 20 opted-in accounts on Tue Oct 13. Decided by: Priya Raman. A1. Priya Raman: Ask Acme whether they still need CSV import for their Monday roster upload. Due: Fri Oct 9 [suggested]. Q1. Do we remove CSV import in v2? Owner: Priya Raman. Needed by: Mon Oct 12. FLAGS - Fake decision: "aligned on killing the CSV import" [04:40] was contested at [04:46]. Logged as Q1, not a decision.
Postmortem notes that name the step, not the person
사용 전
Password reset email incident review, Thu Oct 22, 2026, 2:00 to 3:00 PM ET. My notes. There: Marco Diaz (Engineering lead, incident lead), Sam Lee, Dana Okafor, me (Priya Raman). - Wed Oct 21, 7:05 to 10:50 AM ET: reset and invite emails stuck in the queue. 212 users locked out, 38 tickets - Marco rotated the email provider key Tue night and forgot prod. that's the whole story - first signal was Sam's ticket spike at 9:40, no alert fired - MD: from now on we only rotate keys weekdays 10 to 4 ET - MD: we just need to be more careful with rotations - MD adds "update prod secret" step to the rotation runbook, Monday - alert on queue depth, SL says over 500 for 10 min - email the 212 users? discussed - I left at 2:40 for board prep
사용 후
CAPTURE: Password reset email incident review, Thu Oct 22, 2026 Attendees: Priya Raman, Marco Diaz, Sam Lee, Dana Okafor. Absent: none. Source: notes, 2:00 to 2:40 PM of a 60-min meeting DECISIONS D1. Email provider keys are rotated only on weekdays between 10:00 AM and 4:00 PM ET, from Thu Oct 22. Decided by: Marco Diaz. Why: the Tue Oct 20 evening rotation skipped the production secret, and nothing alerted until the ticket spike at 9:40 AM on Wed Oct 21. Revisit: No. ACTION ITEMS A1. Marco Diaz: Add an "update the production secret" step to the email key rotation runbook. Due: Mon Oct 26. Done when: the runbook change is merged. A2. Marco Diaz [suggested]: Add an alert when the email queue holds more than 500 messages for 10 minutes. Due: Mon Oct 26 [suggested]. Done when: the alert fires in a staging test. OPEN QUESTIONS Q1. Do we email the 212 locked-out users, and with what wording? Owner: Sam Lee [suggested]. Needed by: Fri Oct 23 [suggested]. RISKS None raised. FLAGS - Blame removed: "Marco rotated the key Tue night and forgot prod" is recorded as the step that failed, a rotation runbook with no production secret step. Incident captures name the system or the step, never a person. - Not an action: "be more careful with rotations". D1 and A1 replace it with a rotation window and a named runbook step. - Orphan action: the queue alert had no owner. Suggested Marco Diaz, who leads the incident. The threshold of 500 messages for 10 minutes is Sam's proposal [confirm]. - "Discussed" is not a decision: emailing the 212 users is Q1, suggested for Sam Lee, who owns the tickets. - Initials: MD is Marco Diaz, SL is Sam Lee. "Monday" is Mon Oct 26. - Last 20 minutes missing; decisions may be incomplete. Your notes stop at 2:40 PM, before what went well and the read-back.
Brief for a pricing decision meeting
사용 전
Prep me for tomorrow's pricing meeting. Invite: Starter plan pricing decision, Tue Oct 13, 2:00 to 2:45 PM ET. Elena Park (CEO), Raj Patel (Finance lead), Owen Brooks (Head of Sales), me (organizer). Last capture, Sep 29: Q1 Raj: do we keep existing Starter customers at $19? A3 Owen: win/loss notes from the last 30 Starter deals, due Wed Oct 7. My notes: memo went out Friday. Haven't seen Owen's notes. Elena decides, and wants this closed tomorrow. Memo (1,100 words): A keep $19. B $24 for new customers from Nov 1. C $24 for everyone after 3 months. Recommend B: +$41k ARR in 12 months, assuming 6% lower conversion. Orbit charges $29.
사용 후
BRIEF: Starter plan pricing decision When: Tue Oct 13, 2:00 PM ET, 45 min Type: Decision meeting Goal: We leave with Elena's decision on Starter pricing from Sun Nov 1, including what existing customers pay. Attendees: - Elena Park, CEO, decider: wants this closed tomorrow. You need: a decision in the room, or the date she will decide. - Raj Patel, Finance lead: owns the grandfathering question (Q1). You need: his recommendation. - Owen Brooks, Head of Sales: owns the win/loss notes (A3). You need: his evidence on price, or his position without it. Open from last time: - Q1 Raj Patel: Do we keep existing Starter customers at $19? Needed by Tue Oct 13. Status: unknown. - A3 Owen Brooks: Win/loss notes from the last 30 Starter deals. Due Wed Oct 7. Status: late. 3 questions to settle: 1. Do we choose option B, $24 for new customers only from Sun Nov 1, yes or no? 2. Do existing Starter customers stay at $19 permanently, and if not, from what date do they move? 3. Who tells the sales team and existing customers, and by what date? Pre-read: Starter pricing memo, 5 min read - Options: A keeps $19; B charges $24 to new customers from Nov 1; C moves everyone to $24 after 3 months. - Recommendation is B: +$41k ARR in 12 months, assuming 6% lower conversion. - Orbit charges $29 for a comparable plan. You owe: the memo, sent Fri Oct 9. Nothing else on record. Watch for: Owen argues price will hurt conversion, and A3 is late. If it happens: ask Elena to decide B with a revisit trigger: review if November conversion falls more than 6% below October. Agenda: - 2:00 to 2:03 The question, and Elena decides today (Priya) - 2:03 to 2:10 Silent reading (All) - 2:10 to 2:28 Concerns, strongest first (All) - 2:28 to 2:40 Elena decides, or names what is missing and the date (Elena) - 2:40 to 2:45 Read-back: decision, why, revisit, who tells whom (Priya)
Client-safe recap email
사용 전
CAPTURE: Acme quarterly review, Thu Oct 15, 2026 Attendees: Lena Novak, Tom Reyes (Acme); Priya Raman, Sam Lee (Lumen). Absent: none. DECISIONS D1. Acme moves its 340 seats to onboarding v2 on Mon Nov 2. Decided by: Lena Novak. Why: their pilot team finished the beta. Revisit: No. ACTION ITEMS A1. Priya Raman: Send Acme the v2 migration timeline. Due: Fri Oct 16. Done when: timeline emailed. A2. Sam Lee: Send Acme the v2 admin guide. Due: Mon Oct 19. Done when: guide emailed. A3. Tom Reyes: Share the SSO metadata file with Lumen. Due: Fri Oct 23. Done when: file received. OPEN QUESTIONS Q1. Can Acme keep CSV roster import after Nov 2? Owner: Priya Raman. Needed by: Fri Oct 23. RISKS R1. Lena leaves Acme in December; the Feb 1 renewal has no second champion. Signal: no new sponsor named by Dec 1. Owner: Sam Lee. You: client recap email to Lena and Tom, please.
사용 후
Subject: Acme and Lumen: next steps from Oct 15 Hi Lena and Tom, Thank you for the time today. Here is what we agreed, so we are working from the same list. What we agreed - Acme moves its 340 seats to onboarding v2 on Mon Nov 2. Next steps - Lumen: send the v2 migration timeline, by Fri Oct 16 (Priya Raman) - Lumen: send the v2 admin guide, by Mon Oct 19 (Sam Lee) - Acme: share the SSO metadata file, by Fri Oct 23 (Tom Reyes) Still open - Whether Acme can keep CSV roster import after Nov 2. We will come back to you by Fri Oct 23. If I missed anything, reply here and I will update the list. Priya Left out: R1, the champion risk. Internal risks never go to clients. Draft only; nothing has been sent.
구성
- meeting-war-room.zip
Kit 소개
Paste a meeting transcript or rough notes and get back the decisions, every action item with one owner and a due date, the open questions and the risks, then a recap ready for Slack or email. Before a meeting, the same skill writes a one-page brief that ends in the 3 questions you need settled. It works in Claude, ChatGPT, Codex and Cursor, and installs in 5 minutes.
What you get
- Three modes. BRIEF before the meeting, CAPTURE during or after it, RECAP for the send-out. The skill picks the mode from what you paste.
- Agenda templates for six meeting types: 1:1, weekly team, decision meeting, client call, board or investor update, incident review. Each has timeboxes, the pre-work to ask for and the mistakes to avoid in that meeting.
- A four-check test for real decisions. It catches "I think we're all aligned, right?" and moves it to open questions instead of letting it pass as decided.
- Action item rules. One owner, verb first, a calendar date, and a "Done when". A rewrite table turns "look into" and "circle back" into deliverables with dates.
- Orphan action fixes. No owner, no date, passive voice or an absent owner: each gets a suggested fix that you confirm.
- Transcript cleanup rules. Speaker labels mapped to names, "Friday" turned into a real date, filler removed, numbers kept word for word.
- Recap templates for Slack, internal email, client email, 1:1 messages, board email and absent owners, plus a nudge ladder for overdue items.
- Two worked examples: a messy 8-minute transcript turned into a finished capture and recap, and a brief for a pricing decision meeting.
Every output uses the same blocks: DECISIONS, ACTION ITEMS, OPEN QUESTIONS and RISKS. You can paste them into Notion, Slack or a doc without reformatting.
Who it is for
- Managers who run a weekly team meeting and 1:1s and keep losing track of who said they would do what.
- Founders and executives preparing for board, investor and client meetings.
- Chiefs of staff, program managers and EAs who write the recap for someone else's meeting.
- Anyone whose meeting tool already produces a transcript that nobody reads.
What it will not do
- Join, record or transcribe meetings. It works from the transcript or notes you give it.
- Send anything. Recaps and nudges are drafts for you to send.
- Make up owners, dates or decisions. Gaps are marked [confirm] and proposals [suggested], for you to settle before anything goes out.
- Write formal board minutes or HR records. It captures the discussion and tells you who owns the official record.
- Run on a schedule. For evening prep and Friday chasing, see the Meeting War Room Bot or Dot.
리뷰
아직 리뷰가 없어요.
회의 Kit 더 보기
Meeting War Room Kit
A brief before every meeting, then decisions, owners and dates that get chased to done.
Meeting War Room Bot
Briefs for tomorrow's meetings every evening, and a Friday chase of overdue actions.
Meeting War Room Dot
Your dot preps your meetings, keeps the decision log in Notion and chases late owners.