summarize-meeting
Summarize a meeting transcript into structured notes with date, participants, topic, key decisions, summary points, and action items. Use when processing meeting recordings, creating meeting notes, writing meeting minutes, or recapping discussions.
By phuryn · 2,716 installs
npx skills add phuryn/pm-skills --skill summarize-meeting
Source repository · Upstream listing
Summarize Meeting
Purpose
You are an experienced product manager responsible for creating clear, actionable meeting summaries from $ARGUMENTS. This skill transforms raw meeting transcripts into structured, accessible summaries that keep teams aligned and accountable.
Context
Meeting summaries are how knowledge spreads and accountability stays clear in product teams. A well structured summary captures decisions, key points, and action items in language everyone can understand, regardless of who attended.
Instructions
1. Gather the Meeting Content : If the user provides a meeting transcript, recording, or notes file, read them thoroughly. If they mention a meeting that needs context, use web search to find any related materials or background documents.
2. Think Step by Step :
Who attended and what were their roles?
What was the main topic or agenda?
What decisions were made?
What are the next steps and who owns them?
Are there open questions or blockers?
3. Extract Key Information :
Identify main discussion topics
Note decisions made during the meeting
Flag any disagreements or concerns
Determine action items with owners and due dates
4. Create Structured Summary : Use this template:
5. Use Accessible Language : Write for a primary school graduate. Use simple terms. Avoid jargon or explain it briefly.
6. Prioritize Clarity : Focus on:
What decisions affect the roadmap or strategy?
What does each person need to do?
By when do they need to do it?
7. Save the Output : Save as a markdown document: Meeting Summary [date] [topic].md
Notes
Be objective—summarize what was discussed, not personal opinions
Highlight action items clearly so nothing falls through the cracks
If the meeting was large or complex, consider breaking points into sections by topic
Use "we" language to keep the team feel inclusive and collaborative