calendar-prep

name: calendar-prepdescription: >  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.license: MIT + Commons Clausemetadata:   version: 1.0.0  author: borghei  category: personal-productivity  domain: meetings  updated: 2026-05-04  python-tools: meeting_prep_briefer.py  tech-stack: meetings, productivity  tags:     - meeting-prep    - briefing    - calendar    - one-on-ones

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, settle the inputs below. When one is missing or vague and would change the result, ask about it; when it wouldn't, use a sensible default and say which one you used.

• Meeting type & attendees: customer call vs board vs 1:1 changes the briefing's structure, tone, and emphasis.
• Your goal / decision sought: this becomes the front-loaded first line of the briefing.
• Prior context: last contact, open issues, current status; without it the briefing is generic and useless.

Ask about the two or three inputs that matter most for this request, not the whole list. If the user wants a result straight away, produce it and state your assumptions at the top.

---

Quick Start

1. Fill in assets/meeting_input.json with attendees, context, decisions needed, supporting links
2. Run: python scripts/meeting_prep_briefer.py meeting_input.json
3. Read the briefing 5 minutes before the meeting

---

Core Workflows

Workflow 1: Customer Call Prep

1. Pull the customer's recent activity, last meeting notes, current account status
2. Fill input JSON with: attendees, last contact, open issues, your goal, decisions you're trying to make
3. Run briefer
4. 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

1. Pull metrics dashboard, prior board deck, last investor update
2. Build input JSON; emphasize decisions sought from the board
3. Pair output with documents/pptx-toolkit/ deck audit

Time Estimate: 30-60 minutes per board meeting.

Workflow 3: Manager 1:1 Prep

1. Compress the past two weeks: top 3 wins, top 3 challenges, top 3 asks
2. Run briefer
3. 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. --json prints the parsed input back as JSON, not the briefing; use the default markdown output for the briefing itself.

python scripts/meeting_prep_briefer.py meeting_input.json
python scripts/meeting_prep_briefer.py meeting_input.json --json

---

Scope & Limitations

In Scope:

• One-page markdown briefings built from a structured JSON input (assets/meeting_input.json) by meeting_prep_briefer.py.
• Briefing structure that front-loads the goal and lists attendees and their positions, decisions sought, questions and talking points.
• Workflows for customer calls, board and investor meetings, and manager 1:1s.
• Briefing methodology in references/briefing_methodology.md: when a briefing helps, when it is overhead, and what goes in it.

Out of Scope:

• Reading calendars, email or CRM records. The skill does not pull meeting context from any system.
• Building a board deck (see c-level-advisor/board-deck-builder/) or auditing a .pptx file (see documents/pptx-toolkit/).
• Capturing decisions and action items after the meeting (see personal-productivity/meeting-insights/).
• Preparing for meetings with a legal focus (see legal/legal-meeting-briefing/).

Important Caveats:

• The briefer formats what is in the input file. It does not research attendees or check facts, so the briefing is only as current as the context entered.
• Attendee positions, leverage and talking points are the user's own judgement. The tool does not infer them.
• The --json flag outputs the parsed input, not a JSON version of the briefing.

---

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.