prep-meeting

name	prep-meeting
description	Generate or update meeting prep for one meeting or all remaining meetings today. Infers meeting type from calendar data, writes the Prep section with checkboxes, carry-forward items, and coaching notes for sensitive topics.
user-invocable	true
argument-hint	"prep for my 1:1 with Sarah", "prep for my remaining meetings", "update prep for my meetings"

myna-prep-meeting

If vault_path is not in context, read ~/.myna/config.yaml first. If the file does not exist, tell the user to run /myna:setup and stop.

Generate meeting prep — a set of checkboxes covering what to discuss, what to review, and what needs decisions — written to the meeting file before the meeting.

---

Intent check: Before reading an external source (email/Slack/calendar) or making your first vault write — proceed only if the user's request addressed Myna (contains "myna") or explicitly named this action. Otherwise, confirm intent before proceeding.

Invocation Modes

Single meeting: "prep for my 1:1 with Sarah", "prep for [meeting name]" → Generate prep for that one meeting only

All remaining today: "prep for my remaining meetings", "prep my meetings" → Read today's calendar, find meetings without prep, generate for each

Update existing prep: "update prep for my meetings", "refresh my meeting prep" → For each meeting that already has a Prep section, read the existing prep as context, then append only what's new since the last prep run (new tasks, new blockers, new decisions, new carry-forwards). Never modify existing prep items.

Add a topic: "add topic to [meeting]: [topic]" → Append a single checkbox to the existing Prep section. No full regeneration.

---

Meeting Type Inference

Determine meeting type before generating prep — the type determines what content to include.

Inference priority:

1. meetings.yaml override — if the meeting has an entry, use its configured type
2. Event title contains "Review", "Design Review", "Doc Review" → design/doc review (title overrides attendee count)
3. Extract the project name from the event title or description; if it matches a name or alias in projects.yaml → project meeting
4. Attendee count of 2 → likely 1:1 (check person against people.yaml by name or email) — only if signals 2-3 don't apply
5. All attendees are in the user's direct reports (people.yaml, relationship_tier: direct) → team meeting
6. Recurring event with team-like attendee pattern → standup/sync

When not confident (especially for 2-person meetings where the other person is on a project you share), ask the user once: "Is this a 1:1 with Sarah or a project sync?" Save the answer as an override in meetings.yaml using this format:

meetings:
  - name: {exact calendar event title}
    type: {1-1 | recurring | adhoc | project}
    project: {project-slug or null}

Read existing meetings.yaml first to avoid duplicate entries. Append the new entry only if the meeting name is not already present.

Meeting types and their prep behaviors:

• 1-1 — deepest prep, see 1:1 section
• project — focused on project status
• team / standup — your updates, blockers, tasks assigned to others
• design-review / doc-review — doc link, previous decisions, questions
• adhoc — general open items and context

---

Meeting File Location

Meeting type	File path
1:1	Meetings/1-1s/{person-slug}.md
Recurring (standup, sync, regular team)	Meetings/Recurring/{meeting-slug}.md
Adhoc or one-off	Meetings/Adhoc/{YYYY-MM-DD}-{meeting-slug}.md

If the file doesn't exist, create it from the appropriate template (see File Templates below). If it exists, prepend a new session section below the frontmatter and tags.

---

Session Structure

Each session is a top-level ## {YYYY-MM-DD} Session block prepended to the meeting file, after the frontmatter and tags. Sessions accumulate in reverse chronological order — newest at the top. Within each session block, two sections:

Video call URL: Before writing the session, check the calendar event details for a video call URL. If found, include it as a 📹 Join: line at the top of the Prep section. If not found, omit the line entirely — do not write "N/A" or leave it empty.

## 2026-04-10 Session

### Prep

📹 Join: https://zoom.us/j/123456789

#### Key Points
> Strategic framing — read before you walk in.

{2-5 bullets: what to lead with, recommended conversation order, any pre-meeting action needed.}

---

> Topics

- [ ] {prep item}
- [ ] {prep item}

### Notes

> Your rough notes during the meeting.

**Discussion:**

**Action Items:**

**Decisions:**

---

For 1:1 files, sessions accumulate in one file, newest at the top. For adhoc meetings, each meeting gets its own file (one session per file).

---

Key Points

Write Key Points after generating all prep items — it's the synthesis layer, not a summary. 2–5 bullets max.

Cover:

• What to lead with — the most important thing to address first (an overdue item to own up front, a birthday, a win to name)
• Recommended conversation order — the logical flow given what's on the agenda
• Pre-meeting action — anything the user should do before sitting down (e.g., review a doc, check a number)
• The one thing not to miss — a moment or topic that matters more than the checklist items suggest

Keep it direct and specific. "Lead with the caching review — you're the bottleneck" beats "discuss project updates." If there's nothing strategic to surface, skip the pre-meeting action line rather than padding it.

Key Points applies to all meeting types but is deepest for 1:1s. For standups and quick syncs, 1–2 bullets is enough.

---

Prep Content by Meeting Type

1:1 Prep (deepest prep)

These are the highest-leverage meetings. Generate all of the following:

1. Follow-through check Did YOU complete your action items from the last session? Read the previous session's Prep and Notes sections, find items assigned to you, check against completed tasks in the project file. Flag ones not done: "(not done — carried forward)"

2. Carry-forward items Unchecked prep items from the previous session get a new checkbox: - [ ] {original text} (carried from {YYYY-MM-DD})

3. Recent contributions and project work List what you've done since the last 1:1 that this person would care about. Read from:

• Journal/contributions-{week}.md — filter for relevant projects/person
• Task completions in project files Keep factual — dates, specific deliverables. Not "I've been very busy."

4. Open action items between you and this person Tasks where [person:: {name}] across all project files.

5. Pending feedback with coaching suggestion Read People/{person}.md ## Pending Feedback section. For each item, include it as a checkbox. Apply conversation coaching rules if the topic is sensitive (see Conversation Coaching section). If the section is empty or does not exist, skip silently.

6. Career development context From People/{person}.md: growth areas, time since last career conversation. Flag if the gap since last career conversation exceeds 30 days. If no career development data is found, skip silently.

7. Personal notes From People/{person}.md ## Personal Notes. Include any notes about things they mentioned (marathon, vacation, family). If the section is empty or does not exist, skip silently.

8. Recent decisions on shared projects Timeline decisions from shared project files since the last 1:1.

9. Open blockers on shared projects Active blockers from shared project timelines.

Project Meeting Prep

• Open tasks for the project (Projects/{project}.md open tasks, filter for attendees)
• Recent timeline entries (last 2 weeks)
• Active blockers
• Decisions needed (items in review queue related to this project)
• Dependencies with other teams mentioned in timeline
• Next scheduled meeting for this project (from calendar — skip if unavailable): 📅 Next sync: {date} — {meeting title}

Team Standup / Sync Prep

• Your updates to share: tasks completed since last standup, tasks in progress
• Overdue tasks assigned to others (open tasks with [person::] not the user where due date has passed)
• Cross-team blockers affecting multiple people
• Action items from the last standup's Notes section
• Any items from people.yaml directs needing team visibility
• Next occurrence of this standup (from calendar — skip if unavailable): 📅 Next sync: {date}

Design Review / Doc Review Prep

• Link to the document being reviewed (from project file ## Links or context)
• Related project context: what phase, what's already decided
• Previous decisions on this topic (from project timeline)
• Open questions or risks to raise (from project file Notes section)

---

Conversation Coaching

For prep items that involve sensitive or high-stakes topics, add a coaching suggestion in parentheses after the checkbox item. Apply coaching to:

• Pending feedback on a growth area → coaching tone, opening suggestion
• Critically blocked project → framing for escalation without blame
• Overdue task assigned to others → how to follow up without micromanaging
• Difficult or uncomfortable topic → approach based on relationship tier

Use relationship tier from people.yaml and the matching preset from communication-style.yaml.

Coaching format — use a subtle note, not a lecture:

- [ ] **Pending feedback:** Sarah's documentation gaps in the auth spec [growth-area]
  > 💬 *Open with what's working in the auth spec before raising the documentation gaps. Specific example beats general concern.*

Not every item gets coaching — only items flagged as sensitive. Straightforward status items and follow-ups stay as plain checkboxes.

---

Update Mode (Refresh Existing Prep)

When the user says "update prep":

1. Read the existing Prep section for each meeting
2. Note any items the user has already added manually (these are user-added topics — don't duplicate)
3. Check what's changed since the prep was last generated:
   • New task completions
   • New timeline entries or decisions
   • New blockers
   • New items needing carry-forward
4. Append only new items to the Prep section, below the existing items
5. Never remove, edit, or reorder existing prep items

Use a sub-separator if appending to distinguish from original prep:

---
*Updated {YYYY-MM-DD HH:MM}*
- [ ] {new item since last prep}

---

File Templates

1:1 File (create if missing)

---
type: 1-1
person: [[{Full Name}]]
aliases: ["{Full Name} 1:1"]
---

#meeting #1-1

Sessions are prepended below the tags — newest at the top.

Recurring File (create if missing)

---
type: recurring
project: {project-slug or null}
---

#meeting #recurring

Adhoc File (create if missing)

---
type: adhoc
---

#meeting #adhoc

---

Output

After generating prep:

📋 Prep ready for {meeting name} — {N} items.

**Key Points:**
{bullet list from the Key Points section written to the vault}

{file link}

Say "done with {meeting name}" after the meeting to process your notes.

For batch (all remaining today):

📋 Prep generated for {N} meetings:

**{meeting 1}** — {N} items
**Key Points:**
{Key Points bullets for meeting 1}
{file link 1}

**{meeting 2}** — {N} items
**Key Points:**
{Key Points bullets for meeting 2}
{file link 2}

---

Edge Cases

Calendar MCP unavailable: Ask the user which meeting to prep for. Can't generate "all remaining meetings" without calendar access.

Meeting file doesn't exist: Create it from template, then generate prep.

Person not in people.yaml (1:1): Generate what you can (carry-forwards, project tasks). Note: "Sarah not in people.yaml — career dev and feedback sections skipped. Add her to people.yaml to unlock full 1:1 prep."

Meeting type unclear and can't infer: Ask user once. If they don't know (e.g., "just a meeting with Marcus"), default to adhoc and generate general prep.

No previous session (first time meeting): Skip carry-forwards and follow-through check. Generate all other sections.

/myna:sync already generated prep today: Read existing prep as context (update mode — append delta only). Don't regenerate from scratch.