Prep Meeting

---
name: prep-meeting
description: >
  General meeting preparation — loads context, compiles topics, creates a prep note.
  Use for any meeting. Trigger on phrases like "prepare meeting", "prep meeting",
  "meeting vorbereiten", or "preparation for [meeting name]".
---

# Prep Meeting Skill

Prepares you for any upcoming meeting by loading relevant context, compiling topics
to address, and creating a structured prep note. The note is intentionally lightweight —
Notes and Tasks are filled after the meeting via `/process-meeting`.

---

## CRITICAL RULES

- **Templates**: Always read `04_RESOURCES/Templates/Meeting Preparation.md` before creating a note
- **WikiLinks**: NEVER wrap [[WikiLinks]] in backticks
- **File placement**: Follow the folder routing table below — NEVER save directly in `03_AREAS/Meetings/`
- **No speculation**: Only add topics you have evidence for (hub file, daily note, previous meeting note)

---

## Step 1 — Identify the meeting

Determine: which meeting, which date, which attendees.

If the user gave enough context (e.g. "prep for team standup with Dennis tomorrow"), confirm and proceed.
If unclear, ask: "Which meeting, with whom, and on what date?"

Once identified, determine:
- **Meeting type**: 1:1 with direct report / 1:1 with peer / 1:1 with leadership / team meeting / external / other
- **Attendees**: list of names

---

## Step 2 — Load context

Run all relevant reads in parallel:

1. **Hub files** — for each attendee who has a hub file, read it from `03_AREAS/People/`:
   - Direct reports: `03_AREAS/People/Team/[Name]/[Name].md`
   - Peers: `03_AREAS/People/Peers/[Name]/[Name].md`
   - Leadership: `03_AREAS/People/Leadership/[Name]/[Name].md`
   - Extract: 📌 Next Meeting items, open tasks (👥 / ⌛), Focus Topics

2. **Daily Note** — read `01_ACTIVE/Daily Notes/YYYY-MM-DD.md`
   - Extract: any 📌 @[attendee] items relevant to this meeting

3. **Previous meeting note** — glob `03_AREAS/**/*[Name or MeetingKeyword]*.md` for the most recent note of this recurring meeting type
   - Extract: open action items, unresolved topics

4. **Meeting Preparation template** — read `04_RESOURCES/Templates/Meeting Preparation.md`

---

## Step 3 — Compile "My Topics & Questions"

From all loaded context, compile a deduplicated list of topics to raise:

- 📌 items from hub files and daily note (primary source)
- Open tasks or waiting-for items that need a status update
- Unresolved items from the previous meeting note
- Any context the user provided in the prompt

Keep topics concise: one line each. No invented items.

---

## Step 4 — Create the prep note

Create the file using the template. Fill in **only the `## Meeting Preparation` section**:

- **Frontmatter**: apply standard meeting frontmatter
- **Header**: date + meeting name
- **Meeting Date / Type / Attendees**: fill from Step 1
- **My Topics & Questions**: insert compiled topics as a prioritized bullet list
- **Open Tasks & Delegations**: pull from hub file tasks section

**CRITICAL — `## Meeting Documentation` section**: Leave completely untouched with template placeholders. These are filled after the meeting via `/process-meeting`.

**Frontmatter:**
```yaml
---
tags: [meeting, preparation, YYYY-MM-DD]
up: "[[folder-path]]"
---
```

**File naming:** `YYYY-MM-DD_[Meeting-Name].md`

**Folder routing:**

| Meeting type | Folder |
|---|---|
| 1:1 with direct report | `03_AREAS/People/Team/[Name]/` |
| 1:1 with peer | `03_AREAS/People/Peers/[Name]/` |
| 1:1 with leadership | `03_AREAS/People/Leadership/[Name]/` |
| Recurring team meeting | `03_AREAS/Organization/[MeetingType]/` |
| General / external | `03_AREAS/Organization/` |

---

## Step 5 — Summary

Tell the user briefly:
- File created at [path]
- How many topics are queued
- The 1–2 most important topics to not skip (your judgment based on context)