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-prep
3description: >
4 Generate one-page meeting briefings from structured input (attendees, prior
5 context, decisions needed). Use before customer calls, board meetings, or
6 1:1s to prepare a pre-read or briefing.
7license: MIT + Commons Clause
8metadata:
9 version: 1.0.0
10 author: borghei
11 category: personal-productivity
12 domain: meetings
13 updated: 2026-05-04
14 python-tools: meeting_prep_briefer.py
15 tech-stack: meetings, productivity
16---
17
18# Calendar Prep
19
20Convert structured meeting context into a one-page briefing in seconds.
21
22---
23
24## Keywords
25
26meeting prep, calendar prep, briefing, pre-read, pre-meeting, talking points, agenda, board meeting, customer call, 1:1
27
28---
29
30## Clarify First
31
32Before generating the briefing, confirm these inputs. If any is unknown or vague, ASK — do not assume:
33
34- [ ] **Meeting type & attendees** — customer call vs board vs 1:1 changes the briefing's structure, tone, and emphasis
35- [ ] **Your goal / decision sought** — this becomes the front-loaded first line of the briefing
36- [ ] **Prior context** — last contact, open issues, current status; without it the briefing is generic and useless
37
38Stop 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.
39
40---
41
42## Quick Start
43
441. Fill in `assets/meeting_input.json` with attendees, context, decisions needed, supporting links
452. Run: `python scripts/meeting_prep_briefer.py meeting_input.json`
463. Read the briefing 5 minutes before the meeting
47
48---
49
50## Core Workflows
51
52### Workflow 1: Customer Call Prep
531. Pull the customer's recent activity, last meeting notes, current account status
542. Fill input JSON with: attendees, last contact, open issues, your goal, decisions you're trying to make
553. Run briefer
564. Walk in knowing: what you want, what they want, where you have leverage
57
58**Time Estimate:** 10-15 minutes per major customer call.
59
60### Workflow 2: Board / Investor Meeting Prep
611. Pull metrics dashboard, prior board deck, last investor update
622. Build input JSON; emphasize decisions sought from the board
633. Pair output with `documents/pptx-toolkit/` deck audit
64
65**Time Estimate:** 30-60 minutes per board meeting.
66
67### Workflow 3: Manager 1:1 Prep
681. Compress the past two weeks: top 3 wins, top 3 challenges, top 3 asks
692. Run briefer
703. Lead with asks (1:1s default to status; the leverage is in asking)
71
72**Time Estimate:** 5-10 minutes per 1:1.
73
74---
75
76## Tools
77
78### meeting_prep_briefer.py
79
80Reads a structured JSON input describing meeting context and produces a one-page briefing in markdown.
81
82```bash
83python scripts/meeting_prep_briefer.py meeting_input.json
84python scripts/meeting_prep_briefer.py meeting_input.json --json
85```
86
87---
88
89## Reference Guides
90
91- **`references/briefing_methodology.md`** — When briefings help and when they don't, format conventions
92
93---
94
95## Templates
96
97- **`assets/meeting_input.json`** — Input file template
98
99---
100
101## Best Practices
102
103- **One page max.** A 3-page briefing is one you won't read.
104- **Front-load the decision.** The first sentence should be the decision you want.
105- **Read the briefing.** Generating one without reading it is performance theater.
106- **Capture outputs.** Pair with `personal-productivity/meeting-insights/` post-meeting to convert the briefing's questions into the meeting's decisions.
borghei