prep-meetinglisted

# 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. --- ## 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