Meeting Notes

# Meeting Notes

Turn a raw meeting transcript or note dump into a structured set of
decisions, action items, and open questions.

## When to use

Use this skill when the user pastes:
- A Zoom/Meet/Teams transcript
- Raw notes from a call
- A "we decided X, also Y, also someone needs to Z" stream of consciousness
- Bullet-point notes with no structure

## Inputs

A blob of text containing:
- Speaker names (Zoom-style `[Sarah]: …`) — preferred
- Or no names, just notes

Optional:
- `meeting_title` — defaults to "Meeting"
- `date` — ISO format
- `attendees` — list of names

## Output format

```markdown
# <Meeting Title> — <Date>

**Attendees:** <names>

## TL;DR

<1–2 sentence summary of the most important outcome>

## Decisions

1. **<decision in one line>**
   <why, who decided, any condition>

## Action items

| Owner | Action | Due |
|-------|--------|-----|
| Sarah | Draft Q3 budget memo | 2025-03-15 |
| Marcus | Spike on Postgres → Aurora migration | next week |

## Open questions

- <question 1>
- <question 2>

## Discussion notes

- <topic 1 — 1-line note>
- <topic 2>
```

## Process

1. Read the whole input. Don't extract anything yet.
2. Identify **decisions** — places where the group concluded "we will X" or
   "we won't X". A decision is binding; an opinion isn't.
3. Identify **action items** — anything of the form "<person> will <do
   thing> by <when>". If the owner is missing, mark it `?`. If the
   deadline is missing, mark it `tbd`.
4. Identify **open questions** — things the group raised and didn't
   resolve.
5. Capture **discussion notes** — interesting context that didn't become
   a decision but might matter later. Keep these terse.
6. Write the **TL;DR** last, after you know what mattered.

## Disambiguation rules

- "We should probably look into X" → open question, NOT an action item
  unless an owner volunteered.
- "I'll handle X" → action item, owner = the speaker.
- "Let's revisit next quarter" → open question with a "Q3 follow-up" tag.
- A decision needs a clear "we will" or "agreed to". Mere agreement on a
  framing isn't a decision.

## Example

**Input:**
```
[Sarah] Okay so the migration thing — I think we should just do it now
rather than wait.
[Marcus] Agreed, let's do it. I can spike on it next week.
[Priya] What about the auth stuff? We never decided.
[Sarah] Let's table that — Marcus, ping me Thursday.
```

**Output:**
```markdown
# Engineering Sync — 2025-03-10

**Attendees:** Sarah, Marcus, Priya

## TL;DR

Team agreed to do the database migration now rather than defer it; Marcus
will spike on it next week. Auth direction remains unresolved.

## Decisions

1. **Migrate now, not later.**
   Sarah proposed, Marcus agreed. No dissent.

## Action items

| Owner | Action | Due |
|-------|--------|-----|
| Marcus | Spike on database migration | next week |
| Marcus | Ping Sarah re: auth direction | Thursday |

## Open questions

- Auth direction — what are we actually building? (raised by Priya)

## Discussion notes

- Migration was the headline topic; ~5 min spent.
- Auth raised but explicitly tabled.
```

## Hard rules

- Never invent an action item, decision, or attendee.
- If an action item has no owner, write `?` — don't guess.
- If the input is too thin to extract anything, say so and stop.
- Keep discussion notes to one line each. Anyone who needs the full quote
  can read the transcript.