Skill Meeting Flow — End-to-end meeting intelligence. Pre-meeting prep, real-time notes, action items, decision log. Zero dependencies.
╔═══════════════════════════════════════════════════════════════╗
║ ║
║ ┌──────────┐ ┌───────────┐ ┌───────────┐ ║
║ │ PRE-MEET │───▶│ IN-MEETING│───▶│POST-MEETING│ ║
║ │ │ │ │ │ │ ║
║ │ • Agenda │ │ • Notes │ │ • Summary │ ║
║ │ • Research│ │ • Decisions│ │ • Actions │ ║
║ │ • Objectives│ │ • Actions │ │ • Follow-ups│ ║
║ │ │ │ • Parking │ │ • Score │ ║
║ └──────────┘ └───────────┘ └───────────┘ ║
║ ║
║ Pure Markdown · Zero Dependencies · AI Agent Ready ║
╚═══════════════════════════════════════════════════════════════╝
Every professional has 5-10 meetings/week. Most leave with scattered notes, lost action items, and forgotten decisions. This skill fixes that.
Before Skill Meeting Flow:
📝 Random notes in Notion
📧 Action items buried in email
🤔 "Wait, what did we decide last week?"
😩 Meeting ran 30 min over with no clear outcome
🔄 Same questions asked every standup
📉 No idea if a meeting was even worth having
After Skill Meeting Flow:
📋 Structured agenda before every meeting
🔑 Decisions logged with context & rationale
✅ Action items tracked across meetings
📊 Efficiency score tells you if a meeting is worth keeping
🔄 Recurring meetings auto-prep from last session
🌐 Works in English and 中文
Give your AI agent a meeting type and watch it go:
You: I have a sprint planning meeting at 2pm with the backend team.
Agent:
📋 Generated Sprint Planning Agenda
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Date: 2024-01-15 | Duration: 90min
Team: Backend | Sprint: 24
✅ Loaded last sprint's retro notes
✅ 3 carried action items from previous sprint
✅ 2 parking lot items promoted to agenda
Agenda:
1. Review last sprint commitments (10min)
2. Capacity check (5min)
3. Backlog grooming & selection (40min)
4. Commitments & risks (15min)
5. Action items (10min)
Pre-read: [links to backlog, last retro]
Ready to take notes when the meeting starts.
During the meeting, the agent captures everything:
You: Dave said we're migrating to Kubernetes by end of month.
Sarah will write the runbook by Friday.
We decided to delay the API v2 launch to sprint 45.
Agent: Captured:
🔑 Decision: Delay API v2 launch to Sprint 45
Rationale: K8s migration takes priority
Stakeholders: Frontend team, product
✅ Action: Write K8s migration runbook
Assignee: @sarah | Deadline: 2024-01-19 | Priority: 🔴 High
✅ Action: Notify frontend team of API v2 delay
Assignee: @dave | Deadline: 2024-01-16 | Priority: 🟡 Medium
After the meeting, get a complete summary:
📋 Sprint Planning Summary — Sprint 44
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
TL;DR: Backend will focus on K8s migration this sprint.
API v2 delayed to Sprint 45. Runbook due Friday.
Decisions: 2 | Actions: 4 | Duration: 85min
Efficiency Score: 8/10 🟢
Agenda Adherence: 3/3 ✅ Stayed on track
Time Management: 2/3 ⚠️ 5 min over on backlog grooming
Actions Generated: 2/2 ✅ 4 clear action items
Decisions Made: 1/2 ⚠️ Vendor choice deferred
Next sprint prep draft created from this session.
| # | Type | Duration | Best For |
|---|---|---|---|
| 1 | 🏃 Daily Standup | 15min | Quick team sync — yesterday/today/blockers |
| 2 | 🔄 Weekly Sync | 45-60min | Team priorities, metrics, cross-team updates |
| 3 | 🤝 One-on-One | 30min | Manager-report check-in, growth, feedback |
| 4 | 🔍 Retrospective | 60min | What went well, what didn't, improvements |
| 5 | 📅 Sprint Planning | 60-120min | Backlog selection, capacity, commitments |
| 6 | 💡 Brainstorm | 30-60min | Idea generation, clustering, prioritization |
| 7 | 🎯 Client/Demo | 45-60min | Client meetings, product demos, relationship |
| 8 | 📢 All-Hands | 30-60min | Company/team-wide announcements & Q&A |
Each template includes: agenda structure, note-taking format, summary template, and efficiency scoring criteria.
Never lose a decision again. Every decision is recorded with context, rationale, alternatives considered, and stakeholders affected. Searchable across all meetings.
Persistent tracker that spans meetings. Each action has an assignee, deadline, priority, status, and links to follow-up meetings. Items don't fall through the cracks.
Every meeting gets a 10-point score based on:
- Agenda adherence (3pts) — Did you stick to the plan?
- Time management (3pts) — On time? Well-paced?
- Action items generated (2pts) — Clear, assignable outcomes?
- Decisions made (2pts) — Concrete decisions reached?
Scores below 5? That meeting might not need to exist.
Auto-generates next meeting prep by carrying forward:
- Unresolved parking lot items → New agenda items
- Incomplete action items → Review section
- Decisions needing follow-up → Check-in items
Full template support for English and 中文 (Chinese). Auto-detects language and uses appropriate templates.
Works with any calendar — Google, Outlook, CalDAV, or manual entry. Includes automation flows for pre-meeting prep and post-meeting processing.
# 📝 Meeting Notes: Sprint Planning — Backend Team
**Date:** 2024-01-15 | **Start:** 14:00 | **End:** 15:25
**Attendees:** Dave, Sarah, Mike, Lisa | **Absent:** Tom (OOO)
---
## Discussion
### Topic 1: Last Sprint Review
- **Speaker:** Dave
- Completed 8 of 12 story points
- K8s migration spike took longer than expected
- 🔑 **Decision:** Spin off K8s work into dedicated sprint (D-042)
- ✅ **Action:** Document remaining K8s tasks → @mike by 2024-01-17
### Topic 2: Sprint 44 Planning
- **Speaker:** Sarah
- Capacity: 3 full-time, 1 at 50% (Tom on leave)
- Prioritized: K8s migration > Bug fixes > Tech debt
- 🔑 **Decision:** Delay API v2 launch to Sprint 45 (D-043)
- Rationale: K8s migration blocks deployment pipeline
- Stakeholders: Frontend team, product
- ✅ **Action:** Write K8s migration runbook → @sarah by 2024-01-19 🔴
### Topic 3: Bug Triage
- 12 open bugs, 4 P1
- ❓ **Question:** Is the auth timeout bug P1 or P2? → Parking Lot
---
## 🅿️ Parking Lot
- Auth timeout bug priority — needs input from security team
## ⏭️ Next Steps
- Dave to notify frontend team of API v2 delay (tomorrow AM)
- Sarah to start runbook draft
---
## Summary
**Efficiency Score: 8/10** 🟢
| Metric | Score |
|--------|-------|
| Agenda Adherence | 3/3 |
| Time Management | 2/3 |
| Actions Generated | 2/2 |
| Decisions Made | 1/2 |
**Decisions:** 2 | **Actions:** 4 | **Parking Lot:** 1
meetings/
├── 2024/
│ ├── 2024-01-15-standup.md
│ ├── 2024-01-15-1on1-sarah.md
│ ├── 2024-01-15-sprint-planning.md
│ └── 2024-01-15-client-acme.md
├── action-items.md # Persistent action item tracker
└── decision-log.md # Persistent decision log
Meeting note skills have almost zero competition on skill marketplaces. The best competitor has 2 stars. Meanwhile:
- The average professional spends 23 hours/week in meetings
- 71% of meetings are considered unproductive
- $37 billion is wasted on unnecessary meetings annually in the US alone
- Most people leave meetings with no structured record of what was decided or who's doing what
Skill Meeting Flow is a pure-Markdown, zero-dependency skill that gives AI agents everything they need to make meetings actually productive.
MIT — use freely, no attribution required.
Stop losing decisions. Start tracking actions. Make meetings matter.