Meeting Notes Skill
When invoked with /meeting-notes, transform meeting transcripts or rough notes into structured documentation with extracted action items.
When to Use
- After a meeting with stakeholders
- Processing voice memo transcripts
- Converting rough notes into actionable items
- Preparing meeting summaries for follow-up
Input Types Supported
- Voice transcripts - Raw transcription text
- Rough notes - Bullet points or stream of consciousness
- Chat logs - Copied from video calls
- Memory - Summarize from conversation context
Output Template
---
date: YYYY-MM-DD
tags: [meeting, project-name]
related: [[Projects/ProjectName/README]]
---
# Meeting Notes: [Meeting Title]
**Date:** [date]
**Attendees:** [names]
**Project:** [project name]
**Duration:** [if known]
---
## Summary
[2-3 sentence overview of what was discussed and decided]
## Key Discussions
### [Topic 1]
- [Point discussed]
- [Decision made or question raised]
- [Outcome]
### [Topic 2]
- [Point discussed]
- [Decision made or question raised]
- [Outcome]
## Decisions Made
| Decision | Rationale | Owner |
|----------|-----------|-------|
| [what was decided] | [why] | [who owns it] |
## Action Items
### Immediate (This Week)
- [ ] **[Owner]:** [Action item]
- [ ] **[Owner]:** [Action item]
### Waiting On Others
- [ ] **[Person]:** [What they need to provide]
- [ ] **[Person]:** [What they need to provide]
### Future (Can Wait)
- [ ] [Action item for later]
## Credentials/Access Needed
[If any credentials or access was discussed]
| Item | From Whom | For What |
|------|-----------|----------|
| [credential] | [person] | [purpose] |
## Follow-Up Required
**Email to send:**
- To: [recipients]
- Subject: [suggested subject]
- Include: [key points to mention]
**Next Meeting:** [date/time if scheduled]
## Questions/Clarifications Needed
- [Question that came up but wasn't resolved]
- [Thing that needs verification]
## Raw Notes
<details>
<summary>Original input (click to expand)</summary>
[Paste original transcript/notes here for reference]
</details>
Execution Steps
Parse input - Accept transcript, notes, or summarize from conversation
Extract entities:
- People mentioned
- Dates and deadlines
- Technical terms or project names
- Credentials or access discussed
Identify action items:
- Tasks assigned to specific people
- Things waiting on external input
- Decisions that need to be made
Categorize urgency:
- Immediate (this week)
- Waiting on others
- Future/can wait
Generate output in template format
Save to vault at appropriate location:
Sessions/YYYY-MM-DD-meeting-project.mdfor session-type meetingsProjects/Name/meetings/YYYY-MM-DD.mdfor project-specific meetings
Update related STATUS.md if blockers or deadlines changed
Follow-Up Actions
After processing meeting notes, offer to:
- Draft follow-up email summarizing action items
- Update project STATUS.md with new blockers/deadlines
- Create tasks in relevant tracking system
- Update CREDENTIALS_NEEDED.md if new credentials mentioned
Email Draft Format
When drafting follow-up emails:
Subject: [Meeting] - Summary & Action Items - [Date]
Hi [names],
Thanks for meeting today. Here's a quick summary:
**Discussed:**
- [Key point 1]
- [Key point 2]
**Action Items:**
- [Person]: [Task]
- [Person]: [Task]
**Waiting on:**
- [Item needed from someone]
**Next Steps:**
[What happens next]
Let me know if I missed anything.
Best,
[Your name]
Keep emails:
- Plain text (Gmail-ready)
- Concise but complete
- Action-oriented
- Professional but friendly