Summarize Meeting

What Is This?

Overview

The Summarize Meeting skill transforms raw meeting transcripts into structured, professional notes that capture everything a team needs to act on after a discussion. Instead of leaving participants to sift through lengthy recordings or unformatted text, this skill extracts the essential elements and organizes them into a consistent format covering the meeting date, participants, topic, key decisions, summary points, and action items.

This skill is built for product managers and team leads who regularly process meeting recordings and need reliable, repeatable output. It applies a product management perspective to the summarization process, ensuring that decisions are clearly separated from discussion and that action items are specific enough to be tracked. The result is a document that serves both as a historical record and a practical task list.

Whether you are writing formal meeting minutes for a board session or quick recap notes for a daily standup, this skill adapts to the level of formality required. It handles transcripts from video calls, voice recordings, or manually typed notes, making it broadly applicable across different workflows.

Who Should Use This

• Product managers who run sprint reviews, planning sessions, and stakeholder meetings and need structured notes delivered quickly
• Engineering team leads who want a clear record of technical decisions made during architecture or design discussions
• Executive assistants responsible for producing accurate meeting minutes for leadership or board meetings
• Project coordinators tracking action items and owners across multiple concurrent workstreams
• Sales and customer success teams who need call summaries with follow-up tasks after client meetings
• Freelancers and consultants who bill by the hour and want to minimize time spent on administrative documentation

Why Use It?

Problems It Solves

• Raw transcripts are long and difficult to scan, making it hard to locate a specific decision or commitment made during a meeting
• Manual note-taking during meetings splits attention and reduces the quality of participation in the discussion itself
• Inconsistent note formats across team members create confusion when referencing past meetings or auditing decisions
• Action items buried in conversational text often go unassigned or untracked, leading to missed follow-ups
• Preparing meeting minutes from scratch after every session consumes significant time that could be spent on higher-value work

Core Highlights

• Extracts structured fields including date, participants, topic, decisions, summary points, and action items
• Applies a product management lens to distinguish decisions from discussion
• Handles transcripts of varying length and format
• Produces output that is ready to paste into project management tools or shared documents
• Separates action items with clear ownership and due dates when that information is present in the transcript
• Consistent output format reduces cognitive load when reviewing notes from multiple meetings
• Works with transcripts from video conferencing tools, voice-to-text outputs, and manual notes

How to Use It?

Basic Usage

Pass a meeting transcript as the argument to the skill. The skill processes the full text and returns structured notes.

## Using the skill via a CLI tool
pm-skills run summarize-meeting --input "transcript.txt"

## Passing transcript content directly
pm-skills run summarize-meeting "Q3 planning call. Attendees: Sarah, Tom, Raj. We decided to push the launch to October 15..."

Specific Scenarios

Processing a video call transcript: Export the auto-generated transcript from Zoom or Google Meet as a text file, then pass it directly to the skill. The output will include a cleaned participant list and a decision log.

Preparing board meeting minutes: Feed the full session transcript and specify a formal tone in your configuration. The skill will produce minutes suitable for distribution to executives and external stakeholders.

Real-World Examples

A product manager running a weekly sprint review copies the Zoom transcript into the skill and receives structured notes within seconds, which are then posted directly to the team Confluence page. An engineering lead uses the skill after architecture review meetings to generate a decision log that feeds into the project ADR (Architecture Decision Record) repository.

When to Use It?

Use Cases

• Sprint planning and retrospective meetings
• Client discovery and requirements gathering calls
• Executive and board meetings requiring formal minutes
• Daily standups where a written record is needed
• Cross-functional alignment sessions with multiple stakeholders
• Post-incident review meetings with action item tracking
• Sales calls requiring follow-up task documentation
• Vendor evaluation and procurement discussions

Important Notes

Requirements

• A readable transcript in plain text format is required as input
• Speaker labels in the transcript improve participant extraction but are not mandatory
• The transcript should cover a single meeting session for best results