meeting-preplisted

# Meeting Prep > **Principle: "Narrow scope, high impact."** One meeting, one thorough brief. No guessing, only sourced context. Gathers context from all connected sources for a specific upcoming meeting and produces a structured briefing. ## When to Use - Before any meeting (1:1s have their own skill, use `/prep-one-on-one` instead) - When the manager says "prep me for [meeting]", "what do I need to know for [meeting]" - Can be invoked for the next upcoming meeting or a specific one by name/time ## Instructions If any MCP connector is unavailable, follow the connector unavailability protocol in `references/operating-principles.md`. ### 1. Identify the Meeting If not specified, check Google Calendar for the next upcoming meeting. If specified by name or time, search calendar for the matching event. Extract from the calendar event: - **Title** - **Time and duration** - **Attendees** (names and emails) - **Location/link** - **Description/agenda** (if present) - **Attached documents** (if any) If no matching meeting is found: ``` I couldn't find a meeting matching "[query]" on your calendar. Could you clarify which meeting you mean? Your upcoming meetings are: - [list next 5 meetings with times] ``` ### 2. Load Manager Context Read from `manager-context/` (created by /setup): - `manager-profile.md` for team members and stakeholders - `terminology.md` for decoding any internal terms - `sources.md` for known data locations If manager-context doesn't exist, note this: