summarize-meeting
The summarize-meeting skill transforms meeting transcripts or recordings into structured documentation by extracting participants, topics, key decisions, and action items. Use this skill when creating formal meeting minutes, processing recorded discussions, generating accountability summaries for distributed teams, or converting informal meeting notes into accessible reference materials that clarify next steps and decision ownership.
git clone --depth 1 https://github.com/phuryn/pm-skills /tmp/summarize-meeting && cp -r /tmp/summarize-meeting/pm-execution/skills/summarize-meeting ~/.claude/skills/summarize-meetingSKILL.md
# 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: ``` ## Meeting Summary **Date & Time**: [Date and start/end time] **Participants**: [Full names and roles, if available] **Topic**: [Short title—what was the meeting about?] **Summary** - **Point 1**: [Key discussion point or decision] - **Point 2**: [Key discussion point or decision] - **Point 3**: [Key discussion point or decision] - [Additional points as needed] **Action Items** | Due Date | Owner | Action | |----------|-------|--------| | [Date] | [Name] | [What needs to happen] | | [Date] | [Name] | [What needs to happen] | **Decisions Made** - [Decision 1] - [Decision 2] **Open Questions** - [Unresolved question 1] - [Unresolved question 2] ``` 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
Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
Analyze and prioritize a list of feature requests by theme, strategic alignment, impact, effort, and risk. Use when reviewing customer feature requests, triaging a backlog, or making prioritization decisions.
Generate an Ansoff Matrix analysis mapping growth strategies across market penetration, market development, product development, and diversification. Use when considering growth options, planning market expansion, or evaluating strategic growth paths.
Identify the first beachhead market segment for a product launch. Evaluates segments against burning pain, willingness to pay, winnable market share, and referral potential. Use when choosing a first market, targeting an initial customer segment, or planning market entry strategy.
Design experiments to test assumptions for an existing product — prototypes, A/B tests, spikes, and other low-effort validation methods. Use when validating assumptions, testing feature ideas cheaply, or planning product experiments.
Design lean startup experiments (pretotypes) for a new product. Creates XYZ hypotheses and suggests low-effort validation methods like landing pages, explainer videos, and pre-orders. Use when validating a new product idea, creating pretotypes, or testing market demand.
Brainstorm product ideas for an existing product using multi-perspective ideation from PM, Designer, and Engineer viewpoints. Use when generating new feature ideas, brainstorming solutions for an identified opportunity, or ideating with a product trio.
Brainstorm feature ideas for a new product in initial discovery from PM, Designer, and Engineer perspectives. Use when starting product discovery for a new product, exploring features for a startup idea, or doing initial ideation.