meeting-prep-briefer

Meeting Prep Briefer

This skill generates a structured per-meeting briefing document for busy managers and individual contributors. Given a daily schedule (pasted inline or read from a local file) and any available workspace context files (project notes, participant notes, previous meeting notes), it produces a brief for each meeting with participants, context, open questions, and a suggested agenda — entirely from local files, no external integrations required.

Input: Daily schedule (inline text or local file path) + workspace context files (auto-scanned).

Output: Structured markdown brief (inline response). Optionally saved to output/meeting-brief-YYYY-MM-DD.md on request.

---

Language Detection

Detect the user's language from their message:

• If Russian (or contains Cyrillic): respond in Russian
• If English (or other Latin-script language): respond in English
• If ambiguous: default to English

---

Instructions

Step 1: Parse Input

1. Check if the user provided an inline schedule (list of meetings in their message) or a file path.

   • Inline: parse meetings directly from the message.
   • File path: read the specified file from the workspace. If the file does not exist, return: "File not found: {path}. Please check the path or paste the schedule directly."

2. If no schedule is provided at all, return: "Please paste your meeting schedule or provide a path to a schedule file (e.g., today.md)." Stop — do not generate output.

3. Parse the schedule into a list of meetings. Each meeting must have at minimum a time and a title. Participants are optional.

   • Accepted formats: 10:00 — Team Sync, 10:00 Team Sync (Alice, Bob), 10:00 | Team Sync | Alice, Bob, or similar time + title patterns.
   • If the schedule is completely unparseable (no recognisable time+title structure), return: "Could not parse meeting schedule. Please use a format like: 10:00 — Team Sync (Alice, Bob)." Stop.

4. Determine the brief date: use today's date unless the user specifies another date.