Meeting

Meeting

Usage

• /meeting {title} — Create a meeting note with the given title and today's date.
• /meeting {title} folder={subfolder} — Create in a specific subfolder under Meetings/.
• /meeting (no args) — List today's Google Calendar events and let the user pick one. (Requires gws + Calendar — see SETUP.md and google-workspace-cli.)
• /meeting wrap <path> — Wrap up an existing meeting by running /mail-transcripts, /cache-notes, /fill-participants, and /followup-todos in sequence, with a single commit at the end.
• /meeting wrap pending [<dates>] — Find meetings missing any wrap step and wrap them in sequence. Optional date filter (see Mode D).

File Naming

Format: {Title} - YYYY-MM-DD.md

Examples:

• Engineering - Weekly check-in - 2026-02-18.md
• Jane x Alex Sync - 2026-02-23.md
• Alert System Brainstorm and Requirement Gathering - 2026-02-06.md

Exception — Scrum dailies in Meetings/Engineering/Scrum/ use just YYYY-MM-DD.md.

Frontmatter

Every meeting note starts with YAML frontmatter:

---
Notes:
created: YYYY-MM-DDTHH:MM:SS±HH:MM
---

• Notes: is left empty (populated later with Google Docs / Otter links).
• created: uses the current local timestamp in ISO 8601 with timezone offset.
• Participants: is intentionally omitted at creation time (filled later by /fill-participants).
• modified: is managed by Obsidian automatically — do NOT set it.

Mode A: Manual Creation

Input: /meeting {title} with optional folder={subfolder}

Workflow

1. Parse arguments: Extract the title and optional folder.
2. Determine folder: If folder= is provided, use Meetings/{subfolder}/. Otherwise, ask the user which subfolder to use. List existing subfolders for convenience.
3. Generate filename: {Title} - YYYY-MM-DD.md using today's date.
4. Check for duplicates: If a file with the same name already exists, warn the user and ask how to proceed.
5. Create the file with frontmatter. If a matching template exists in Templates/, ask the user if they want to apply it as the note body.
6. Confirm by printing the created file path.

Subfolder Shorthand

Accept common abbreviations when provided inline:

Case-insensitive matching. If no shorthand matches and the folder doesn't exist, ask before creating it.

Mode B: Google Calendar Selection

Requires: Google Workspace CLI (gws) with Calendar access (read-only). See SETUP.md and google-workspace-cli.

Input: /meeting (no arguments)

Workflow

1. Fetch today's events from Google Calendar by running gws in the terminal (e.g. gws calendar +agenda --today --format json). See google-workspace-cli.
2. Present a numbered list of today's meetings (title, time, attendees).
3. User picks one (or types a number).
4. Derive the title from the calendar event name.
5. Infer the subfolder from attendees or event title:
   • If all attendees are from one team, suggest that team's folder.
   • If it's a 1:1 (2 attendees), suggest One-on-ones/ or Tech Syncs/.
   • Otherwise, ask the user.
6. Create the file following the same steps as Mode A (steps 3-6).
7. Pre-fill Participants from calendar attendees. See people-resolver for name matching rules. Flag any unmatched attendees.

Mode C: Wrap Up (/meeting wrap)

Input: /meeting wrap <path> — path to an existing meeting note (e.g. Meetings/One-on-ones/Jane x Alex Sync - 2026-02-25.md)

If <path> is omitted, list today's meeting files under Meetings/ and let the user pick one.

Workflow

This is a sequenced workflow — sub-skills skip their individual commit steps.

1. /mail-transcripts — Drain the Gemini transcript inbox first so Notes: may be populated before caching. Runs vault-wide (not scoped to <path>).
2. /cache-notes <path> — If Notes: is still empty after mail-transcripts, prompt the user to paste external resource URLs. Then fetch and cache AI transcripts.
3. /fill-participants <path> — Resolve and fill the Participants: frontmatter if missing. If already filled, skip silently.
4. /followup-todos <path> — Extract action items and propose plain bullet follow-ups (no Tasks checkboxes) from the now-cached content and manual notes.
5. Commit — See /commit. Stage all files modified across the sub-skills. Commit message: update: /meeting wrap <path>.

Between each sub-skill, re-read the file (or re-check frontmatter via obsidian property:read) to pick up changes from the previous step.