Meeting notes

---
name: meeting-notes
description: Turns meeting transcripts or rough notes into structured minutes with attendees, decisions, action items, and open questions. Use when the user pastes a transcript, call notes, standup notes, or asks for a meeting recap, minutes, or action list.
---

# Meeting notes

## Goal
Produce minutes a busy teammate can scan in two minutes. Prefer the user's words for decisions. Do not invent attendees, dates, owners, or commitments.

## Workflow
1. Identify meeting title, date, time zone if present, and attendees. If any of these are missing, use `Unknown` and list the gaps at the top.
2. Separate what was discussed from what was decided.
3. Extract action items only when someone accepted a task or the group assigned one. If an owner was not named, set owner to `Unassigned`.
4. Record deadlines only when they were spoken or written. Never invent a date.
5. Flag unresolved debates as open questions, not as decisions.
6. If the transcript is noisy or incomplete, say so and quote the unclear stretch instead of guessing.

## Output template
Use this structure every time:

```markdown
# [Meeting title] — [date or Unknown]

**Attendees:** 
**Missing context:** 

## Summary
[5–8 sentences. What was the meeting for, and what changed because of it?]

## Decisions
- Decision — context in one clause

## Action items
| Action | Owner | Due | Notes |
|---|---|---|---|
| | | | |

## Open questions
- Question — who needs to answer it, if known

## Notable discussion
- Theme: one or two sentences, optional short quote
```

## Rules
- If the source is a transcript, quote lightly (a phrase, not a paragraph) only when a decision hinges on exact wording.
- Do not include small talk, timestamps, or filler unless the user asks for a verbatim record.
- If the user names a house style (for example, “exec recap” or “customer call”), keep the same sections but adjust tone and length.
- After drafting, check that every action item is actually an action and every decision was explicitly made.