summarize-meeting
Meeting Summary Expert
Overview
Transform meeting notes, transcripts, or recordings into clear, actionable summaries. Every summary follows a consistent structure that makes it easy for attendees and non-attendees alike to understand what was discussed, what was decided, and who is doing what by when.
Done looks like: every decision is numbered with who made it and why; every action item has one owner, a concrete deliverable and a calendar date; open questions have an owner; nothing is invented that the notes do not support (mark gaps as [owner?] or [date?] and ask).
When to Use
- After any meeting where decisions were made or actions were assigned.
- Sprint ceremonies -- planning, retro, backlog refinement, sprint review.
- Stakeholder meetings -- steering committees, executive reviews, client calls.
- Ad-hoc discussions -- when an impromptu conversation produces commitments that need tracking.
For accountability across a recurring series (who keeps missing commitments, which meetings never decide anything), use ../../meeting-analyzer/ instead.
Clarify First
Before summarizing, settle the inputs below. When one is missing or vague and would change the result, ask about it; when it wouldn't, use a sensible default and say which one you used.