Calendar Prep
Convert structured meeting context into a one-page briefing in seconds.
Keywords
meeting prep, calendar prep, briefing, pre-read, pre-meeting, talking points, agenda, board meeting, customer call, 1:1
Clarify First
Before generating the briefing, confirm these inputs. If any is unknown or vague, ASK — do not assume:
Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.
Quick Start
- Fill in
assets/meeting_input.json with attendees, context, decisions needed, supporting links
- Run:
python scripts/meeting_prep_briefer.py meeting_input.json
- Read the briefing 5 minutes before the meeting
Core Workflows
Workflow 1: Customer Call Prep
- Pull the customer's recent activity, last meeting notes, current account status
- Fill input JSON with: attendees, last contact, open issues, your goal, decisions you're trying to make
- Run briefer
- Walk in knowing: what you want, what they want, where you have leverage
Time Estimate: 10-15 minutes per major customer call.
Workflow 2: Board / Investor Meeting Prep
- Pull metrics dashboard, prior board deck, last investor update
- Build input JSON; emphasize decisions sought from the board
- Pair output with
documents/pptx-toolkit/ deck audit
Time Estimate: 30-60 minutes per board meeting.
Workflow 3: Manager 1:1 Prep
- Compress the past two weeks: top 3 wins, top 3 challenges, top 3 asks
- Run briefer
- Lead with asks (1:1s default to status; the leverage is in asking)
Time Estimate: 5-10 minutes per 1:1.
Tools
meeting_prep_briefer.py
Reads a structured JSON input describing meeting context and produces a one-page briefing in markdown.
python scripts/meeting_prep_briefer.py meeting_input.json
python scripts/meeting_prep_briefer.py meeting_input.json --json
Reference Guides
references/briefing_methodology.md — When briefings help and when they don't, format conventions
Templates
assets/meeting_input.json — Input file template
Best Practices
- One page max. A 3-page briefing is one you won't read.
- Front-load the decision. The first sentence should be the decision you want.
- Read the briefing. Generating one without reading it is performance theater.
- Capture outputs. Pair with
personal-productivity/meeting-insights/ post-meeting to convert the briefing's questions into the meeting's decisions.
1---2name: calendar-prep3description: Generate one-page meeting briefings from structured input (attendees, prior context, decisions needed). Use before customer calls, board meetings, or 1:1s to prepare a pre-read or briefing.4license: MIT + Commons Clause5---6
7# Calendar Prep
8
9Convert structured meeting context into a one-page briefing in seconds.
10
11---
12
13## Keywords
14
15meeting prep, calendar prep, briefing, pre-read, pre-meeting, talking points, agenda, board meeting, customer call, 1:1
16
17---
18
19## Clarify First
20
21Before generating the briefing, confirm these inputs. If any is unknown or vague, ASK — do not assume:
22
23- [ ] **Meeting type & attendees** — customer call vs board vs 1:1 changes the briefing's structure, tone, and emphasis
24- [ ] **Your goal / decision sought** — this becomes the front-loaded first line of the briefing
25- [ ] **Prior context** — last contact, open issues, current status; without it the briefing is generic and useless
26
27Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.
28
29---
30
31## Quick Start
32
331. Fill in `assets/meeting_input.json` with attendees, context, decisions needed, supporting links
342. Run: `python scripts/meeting_prep_briefer.py meeting_input.json`
353. Read the briefing 5 minutes before the meeting
36
37---
38
39## Core Workflows
40
41### Workflow 1: Customer Call Prep
421. Pull the customer's recent activity, last meeting notes, current account status
432. Fill input JSON with: attendees, last contact, open issues, your goal, decisions you're trying to make
443. Run briefer
454. Walk in knowing: what you want, what they want, where you have leverage
46
47**Time Estimate:** 10-15 minutes per major customer call.
48
49### Workflow 2: Board / Investor Meeting Prep
501. Pull metrics dashboard, prior board deck, last investor update
512. Build input JSON; emphasize decisions sought from the board
523. Pair output with `documents/pptx-toolkit/` deck audit
53
54**Time Estimate:** 30-60 minutes per board meeting.
55
56### Workflow 3: Manager 1:1 Prep
571. Compress the past two weeks: top 3 wins, top 3 challenges, top 3 asks
582. Run briefer
593. Lead with asks (1:1s default to status; the leverage is in asking)
60
61**Time Estimate:** 5-10 minutes per 1:1.
62
63---
64
65## Tools
66
67### meeting_prep_briefer.py
68
69Reads a structured JSON input describing meeting context and produces a one-page briefing in markdown.
70
71```bash
72python scripts/meeting_prep_briefer.py meeting_input.json
73python scripts/meeting_prep_briefer.py meeting_input.json --json
74```
75
76---
77
78## Reference Guides
79
80- **`references/briefing_methodology.md`** — When briefings help and when they don't, format conventions
81
82---
83
84## Templates
85
86- **`assets/meeting_input.json`** — Input file template
87
88---
89
90## Best Practices
91
92- **One page max.** A 3-page briefing is one you won't read.
93- **Front-load the decision.** The first sentence should be the decision you want.
94- **Read the briefing.** Generating one without reading it is performance theater.
95- **Capture outputs.** Pair with `personal-productivity/meeting-insights/` post-meeting to convert the briefing's questions into the meeting's decisions.
borghei