| name | calendar-prep |
| description | Generate one-page meeting briefings from a structured input (attendees, prior context, decisions needed) so you walk into every meeting prepared. Use before customer calls, board meetings, 1:1s, or when the user mentions meeting prep, briefing, pre-read, or pre-meeting.
|
| license | MIT + Commons Clause |
| metadata | {"version":"1.0.0","author":"borghei","category":"personal-productivity","domain":"meetings","updated":"2026-05-04T00:00:00.000Z","python-tools":"meeting_prep_briefer.py","tech-stack":"meetings, productivity"} |
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
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.
