Interactive meeting preparation that searches the normal conversation history\nauthorized by Minutes, synthesizes a relationship brief, and produces talking\npoints — before you walk into the room. Restricted history is excluded from\nthis agent workflow by default and must never be treated as absent evidence.
\nThis is a multi-phase interactive flow, not a single command. Walk the user through each phase using AskUserQuestion, pushing back on vague answers.
\nBefore asking who the user is meeting with, check if upcoming meetings are available from any calendar source. Try these in order — use the first that works:
\n1. Google Calendar MCP (best — most Minutes users have Claude + MCP):\nIf mcp__claude_ai_Google_Calendar__gcal_list_events is available, query today's remaining events:
gcal_list_events(\n timeMin: \"<now ISO, e.g. 2026-03-19T14:00:00>\",\n timeMax: \"<end of day, e.g. 2026-03-19T23:59:59>\",\n condenseEventDetails: false\n)\nDo NOT hardcode a timezone — omit the timeZone parameter so the MCP uses the user's calendar default. This returns attendees, event titles, and times. Parse the results to find the next upcoming meeting with other people (skip all-day events and events with no attendees).
2. gog CLI (if installed):
gog calendar list --today --json -a <account> 2>/dev/null\n3. Apple Calendar (osascript) (every Mac, zero install):
\nosascript -e 'tell application \"Calendar\" to get {summary, start date} of (every event of every calendar whose start date >= (current date) and start date < ((current date) + 1 * days))'\n4. Microsoft 365 / Outlook (m365 CLI) (if installed):
First check if m365 is installed and whether it's logged in:
\ncommand -v m365 2>/dev/null && m365 status --output json 2>/dev/null\nstatus returns \"Logged out\"): ask the user via AskUserQuestion:\n\n\n\"I found the Microsoft 365 CLI (
\nm365) but you're not logged in. Want me to start the login flow so I can pull your Outlook calendar?\"
m365 login --authType browser and wait. Once done, proceed to fetch events below.m365 outlook event list \\\n --userId \"@meId\" \\\n --startDateTime \"$(date -u +%Y-%m-%dT%H:%M:%SZ)\" \\\n --endDateTime \"$(date -u -d '+1 day' +%Y-%m-%dT%H:%M:%SZ 2>/dev/null || date -u -v+1d +%Y-%m-%dT%H:%M:%SZ)\" \\\n --output json 2>/dev/null\nOnly use the result if the command exits with code 0 and returns a non-empty JSON array. Parse the response:
\nevent.subjectevent.start.dateTime (UTC — convert to local time for display)event.attendees[].emailAddress.name (extract first names)event.isAllDay === true, event.isCancelled === true, event.attendees is empty, or event.start.dateTime converted to local time is not today (the now..now+24h UTC window over-fetches so it never misses a local-today event near the UTC date boundary; this trims the next-day-local spillover)5. None available — skip to Phase 1 and ask manually.
\nIf upcoming meetings are found:\nPresent via AskUserQuestion: \"I see you have these meetings coming up today:
\nWhich one are you prepping for?\"
\nOptions: list each meeting + \"None of these — I want to prep for something else\"
\nIf the user picks a meeting, auto-populate the person name and skip Phase 1. Pull attendee names from the calendar event directly.
\nIf no upcoming meetings or calendar unavailable:\nSilently skip to Phase 1. Don't error or apologize — just ask manually.
\nIf Phase 0 already identified the person, skip this phase.
\nOtherwise, ask via AskUserQuestion: \"Who are you meeting with?\"
\nIf the answer is specific (a name like \"Alex\" or \"Case\"):\n→ Check for learned aliases first:
\nnode \"${CLAUDE_PLUGIN_ROOT}/hooks/lib/minutes-learn-cli.mjs\" aliases \"<name>\" 2>/dev/null\nIf aliases exist, search across every returned variant and merge the hits before deciding there is no history.
\n→ Search authorized normal meeting history:
\nminutes search \"<name>\" --limit 50\nAlso search common variations — first name, last name, nickname.
\nIf the answer is vague (\"the team\", \"everyone\", \"my usual meeting\"):\n→ Push back: \"Be specific. Name one person who'll be in the room. I'll search the normal meeting history Minutes is authorized to use.\"
\nIf the answer is a topic (\"the pricing meeting\", \"the Q2 planning call\"):\n→ Adapt to topic-based prep:
\nminutes search \"<topic>\" --limit 20\nSkip the relationship brief and go straight to a topic brief instead.
\nTreat search paths as hints, not capabilities. Reauthorize each selected normal meeting through minutes get \"<exact path>\" --json, require exit status 0, and use only its returned content. Never reopen a search path with the host Read tool. Build a relationship brief from those bounded native results:
Meeting history:
\nRecurring topics:
\nOpen commitments:
\naction_items where assignee matches the user)action_items where assignee matches the other person)open)Decision history:
\ndecisions: frontmatter)Present the relationship brief to the user. Don't ask for approval — just show it and move to Phase 3.
\nIf there are zero past meetings:\nSay: \"I don't have any recorded meetings with [name]. This will be your first meeting on record. What's the context — how do you know them?\"
\nThen skip the relationship brief and go straight to Phase 3 with whatever context the user provides.
\nAsk via AskUserQuestion: \"What's the one thing you'd regret not discussing in this meeting?\"
\nIf the answer is specific (\"finalize the pricing at monthly billing\", \"get a commitment on the hire\"):\n→ Frame talking points around that goal. Connect it to relationship data — e.g., \"Alex's mentioned pricing 3 times recently. She's ready for this conversation.\"
\nIf the answer is vague (\"just catch up\", \"the usual\"):\n→ Push back with evidence: \"Based on your last 3 meetings with Alex, these topics are active: [list]. Which one matters most today?\"
\nIf the user skips (\"I don't know yet\" / \"nothing specific\"):\n→ Accept it. Frame as an open-ended catch-up. Still produce talking points based on open items and recent topics.
\nSave the prep brief to ~/.minutes/preps/ for later pickup by /minutes-debrief:
mkdir -p ~/.minutes/preps\nWrite the file as ~/.minutes/preps/YYYY-MM-DD-{person-first-name}.prep.md with this structure:
---\nperson: {full name}\ndate: {today ISO}\ngoal: {what they want to accomplish}\nmeeting_count: {total past meetings}\n---\n\n## Relationship Brief\n{the brief from Phase 2}\n\n## Talking Points\n{the talking points}\n\n## Goal\n{their stated goal, quoted}\nSet permissions to 0600:
\nchmod 600 ~/.minutes/preps/YYYY-MM-DD-{slug}.prep.md\nUse the person's first name (lowercase) as the slug — e.g., sarah, not sarah-chen — because transcript attendee names are often abbreviated.
End with three beats:
\nSignal reflection — Quote a specific thing the user said during the session.\n\"You said '[exact quote from their AskUserQuestion answers]' — that's your north star for this call.\"
\nAssignment — One concrete real-world action before the meeting. Not \"go build it\" — something specific.\nExamples: \"Text Alex before your call that you want to finalize pricing.\"\n\"Review the competitor grid Case sent you — it's still in your action items.\"
\nNext skill nudge — \"After your call, run /minutes-debrief to capture what you decided and compare it to what you planned.\"
node \"${CLAUDE_PLUGIN_ROOT}/hooks/lib/minutes-learn-cli.mjs\" set-explicit workflow_preference meeting_prep_mode prep \"User explicitly prefers prep\"\nnode \"${CLAUDE_PLUGIN_ROOT}/hooks/lib/minutes-learn-cli.mjs\" set-alias \"Case Wintermute\" \"Case\" \"User confirmed alias\"\ngcal.mcp.claude.com/mcp) is the recommended source for Claude users.m365 login if m365 is installed but the user is not yet authenticated. It's a one-time browser flow. If the user declines, fall through silently.now..now+24h in UTC, which always spans the rest of the user's local day regardless of offset (max UTC offset is under 14h). Times come back in UTC, so convert start.dateTime to local both for the local-today skip check and for display. Use date -d (Linux) or date -jf / date -r (macOS) for conversion, or show the raw UTC time with a (UTC) suffix if conversion is unavailable.sarah not sarah-chen. Transcript attendees are often abbreviated. Debrief matches on first name./minutes-debrief ignores preps older than 48 hours. The user can prep the day before and still get the debrief connection.