borghei/Claude-Skills / project-management/execution/summarize-meeting
summarize-meeting
VerifiedTurns meeting notes or transcripts into a summary of decisions, owned and dated action items, and open questions. Use when writing up a meeting, a recap email or a decision log; for patterns across a series use meeting-analyzer.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 9.0 KB |
| assets/meeting_summary_template.md | markdown | 2.0 KB |
| assets/sample_meetings.json | config | 2.2 KB |
| examples/product-review-may-22.md | markdown | 8.3 KB |
| references/meeting-facilitation-guide.md | markdown | 6.0 KB |
| references/red-flags.md | markdown | 10.0 KB |
| references/summarization-process.md | markdown | 7.1 KB |
| scripts/action_item_tracker.py | script | 8.1 KB |
| scripts/decision_log_builder.py | script | 6.9 KB |
| scripts/meeting_effectiveness_scorer.py | script | 9.1 KB |
references/meeting-facilitation-guide.md
View on GitHub# Meeting Facilitation Guide
## Meeting Types and Best Practices
### Decision Meetings
**Purpose:** Make a specific decision with the right stakeholders in the room.
**Best practices:**
- State the decision to be made in the meeting invite.
- Share pre-read materials at least 24 hours in advance.
- Timebox discussion. If no decision after the allotted time, explicitly decide to defer and state what additional information is needed.
- End with a clear statement of the decision and who will communicate it.
**Summary focus:** The decision, the rationale, and the communication plan.
### Status / Update Meetings
**Purpose:** Align the team on progress, blockers, and next steps.
**Best practices:**
- Keep to 30 minutes or less.
- Use a standing agenda (same structure each time).
- Focus on exceptions -- what is off track, what needs help.
- Do not use the meeting to share information that could be read asynchronously.
**Summary focus:** Blockers, changes to plan, and escalations.
### Brainstorming / Working Sessions
**Purpose:** Generate ideas or solve a problem collaboratively.
**Best practices:**
- Define the problem statement before the meeting.
- Separate idea generation from idea evaluation.
- Use structured techniques (brainwriting, round-robin, dot voting).
- Capture all ideas, even ones not selected.
**Summary focus:** Ideas generated, criteria used to evaluate, and which ideas move forward.
### Planning Meetings
**Purpose:** Agree on scope, timeline, and assignments for upcoming work.
**Best practices:**
- Come with a draft plan, not a blank slate.
- Walk through dependencies and risks.
- Assign owners to every deliverable.
- Confirm the next checkpoint.
**Summary focus:** Commitments (who, what, when), dependencies, and risks.
### Retrospectives
**Purpose:** Reflect on what worked, what did not, and what to change.
**Best practices:**
- Create psychological safety -- no blame, focus on systems.
- Use a structured format (Start-Stop-Continue, 4Ls, Mad-Sad-Glad).
- Limit to 3 actionable improvements per retro.
- Assign owners to improvement actions.
**Summary focus:** Top improvement actions with owners and due dates.
## Note-Taking Strategies
### The Cornell Method (Adapted for Meetings)
Divide your notes into three sections:
1. **Main notes** (during meeting) -- Capture discussion points as they happen.
2. **Key takeaways** (margin) -- Flag decisions, actions, and questions in real-time.
3. **Summary** (bottom) -- Write a 2-3 sentence summary immediately after the meeting.
### Real-Time Action Tagging
As you take notes, prefix actionable items with tags:
- `[ACTION]` -- Something someone needs to do
- `[DECISION]` -- Something that was decided
- `[QUESTION]` -- Something unresolved
- `[RISK]` -- A risk or concern raised
- `[PARKING]` -- Off-topic item to revisit later
This makes post-meeting processing much faster.
### Collaborative Note-Taking
For important meetings, use a shared document where multiple participants contribute:
- One person captures discussion points.
- Another captures actions and decisions.
- Participants correct or clarify in real-time.
- Reduces single-point-of-failure and improves accuracy.
## Action Item Best Practices (SMART Format)
Every action item should be SMART:
| Criterion | Question | Bad Example | Good Example |
|-----------|----------|-------------|--------------|
| **Specific** | What exactly needs to be done? | "Look into the performance issue" | "Profile the dashboard API endpoint and identify the top 3 bottlenecks" |
| **Measurable** | How will we know it is done? | "Improve onboarding" | "Reduce onboarding flow from 8 steps to 5 steps" |
| **Assignable** | Who is the single owner? | "The team will handle it" | "Maria will handle it" |
| **Realistic** | Can it be done in the timeframe? | "Rewrite the entire backend by Friday" | "Draft the migration plan by Friday" |
| **Time-bound** | What is the deadline? | "Do it soon" | "Complete by March 15" |
## Follow-Up Processes
### Within 24 Hours
1. Finalize and distribute the meeting summary.
2. Create tickets for action items in your tracking system (Jira, Linear, Asana).
3. Update any affected project plans or roadmaps.
### At the Next Meeting
1. Review open actions from the previous meeting.
2. Mark completed items and escalate overdue items.
3. Carry forward unresolved questions.
### Weekly
1. Review all open action items across meetings.
2. Follow up with owners on items approaching their due date.
3. Escalate blocked items.
## Meeting Anti-Patterns
### The Status Meeting That Should Be an Email
**Symptom:** Participants take turns reading updates that could be shared asynchronously.
**Fix:** Use async updates (Slack, email, dashboard) and reserve meeting time for discussion of exceptions and decisions.
### The Meeting Without a Decision
**Symptom:** Lots of discussion, no clear outcome. Same topic appears in the next meeting.
**Fix:** State the decision to be made upfront. If the group cannot decide, explicitly state what information is needed and who will gather it.
### The Meeting With Too Many People
**Symptom:** Most attendees are silent. Side conversations happen. Decisions are deferred because "we need to check with so-and-so."
**Fix:** Invite only decision-makers and direct contributors. Share the summary with everyone else.
### The Meeting Without an Agenda
**Symptom:** Discussion meanders. Important topics get squeezed at the end or skipped entirely.
**Fix:** Every meeting invite must include an agenda with time allocations. No agenda, no meeting.
### The Meeting That Runs Over
**Symptom:** Meetings consistently exceed their scheduled time, causing cascading delays.
**Fix:** Appoint a timekeeper. When time is up, decide to either extend (with consent) or schedule a follow-up. Do not silently run over.
### Missing Follow-Through
**Symptom:** Action items are captured but never tracked. The same issues resurface weeks later.
**Fix:** Review previous action items at the start of every recurring meeting. Use a tracking system, not just meeting notes.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |