meeting-noteslisted

## Why this exists, and what I'd change **Why it exists.** Raw transcripts are useless. Action items get lost. Stakeholder updates need extraction. This skill does the extraction work the same way every time, so meetings actually convert into action instead of dying in a Notion doc. **Design tradeoffs.** - **One skill handles every input format.** Otter transcripts, voice memos, bullet notes, Slack threads, or "just tell me what happened." Cost: the prompt has to detect input length and adapt, and quality drops on really short notes where there's not enough signal to extract. - **Action items get inferred owners and dates.** Even when the transcript is fuzzy. Cost: when the source is ambiguous, the skill fills in confident-sounding owners that may be wrong. Always re-read before forwarding. - **Output is a markdown file, not a ticket.** I don't auto-create Linear or Jira tickets by default. Cost: an extra `/create-tickets` step every time, which kills the flow. **What I'd change.** Auto-create tickets in the connected PM tool by default. Make opting out the explicit step, not opting in. --- ## Quick Start **What to provide:** Raw meeting content in any format. ``` /meeting-notes → I'll ask for your content /meeting-notes [paste transcript] → Process immediately /meeting-notes [paste notes] --minimal → Quick-capture format /meeting-notes [paste notes] --slack → Slack-friendly format ``` **Accepted inputs:** Zoom/Otter/Grain transc