SKILL.md — meeting-notes

---
name: meeting-notes
description: >
  Turn a meeting transcript or recording notes into structured minutes:
  decisions, action items with owners, and a short summary. Use when the
  user shares a transcript or says "write up the meeting".
---

# Meeting Notes

## Output, in this order

1. **Two-minute summary** — what the meeting was about and what changed,
   five sentences maximum.
2. **Decisions** — each one sentence, with who made the call if the
   transcript shows it.
3. **Action items** — table: owner, action, due date. An item with no
   owner is listed under "Unowned" so it is visibly nobody's.
4. **Parking lot** — raised but not resolved.

## Rules

- Only what was actually said. No inferred decisions, no invented owners,
  no "presumably". Ambiguity gets a `[unclear]` marker and stays in.
- Names: use them as spoken; if two people share a first name, keep the
  disambiguation the speakers used.
- Numbers, dates, and commitments are quoted exactly — these are the parts
  people fight about later.
- If the transcript is partial or the audio notes say "[inaudible]", the
  minutes say so at the top.

## After writing

Offer exactly one follow-up: filing the action items wherever this
workspace tracks tasks. Do not do it unasked.

Why this shape

Minutes are a trust artifact — the rules bias hard toward only what was said because one invented action item costs more credibility than ten missed ones. The unowned-items section exists because "someone should" is where meeting outcomes go to die.