writing-meeting-notes
Installation
SKILL.md
Writing Meeting Notes
Overview
Turn raw notes/transcript into a structured, skimmable record that makes next steps unambiguous.
When to Use
- Notes are messy, partial, or out of order
- A transcript exists but no one will read it end-to-end
- There were decisions, open questions, or action items to track
When NOT to use
- The meeting is purely social with no decisions or follow-ups
Core Pattern
Separate “what happened” from “what’s next”:
- Summary (context)
- Decisions (committed outcomes)
- Action Items (owner + due date)
- Open Questions / Risks (unresolved)
Quick Reference
Use this template:
- Attendees:
- Context: (1–3 bullets)
- Decisions:
- Action Items: (each item has Owner, Due, Next step)
- Open Questions / Risks:
Implementation
- Scan for explicit decisions (“we will…”, “agreed…”, “we decided…”).
- Extract actions (“X will do Y by Z”) and assign owners if missing (flag if unknown).
- Promote unresolved items into Open Questions / Risks.
- Keep it concise; link to source transcript if needed.
Common Mistakes
- Burying action items in narrative text — always list separately.
- Inventing owners/dates — if absent, mark as “Owner: TBD” / “Due: TBD”.
Related skills
More from danbars/skills
writing-email-subjects
Use when an email draft exists but the subject line is unclear, too long, or needs options tailored to a specific audience and tone.
14triaging-bugs
Use when a bug report is ambiguous or incomplete and you need a consistent way to assess severity, impact, reproducibility, and the next investigative step.
10writing-release-notes
Use when changes are ready to ship and you need to communicate what changed, who it affects, and any required actions without exposing internal-only details.
9