Skip to main content
command CX Codex

meeting-notes — Claude Code command: what it does, how to install

Turns a transcript or rough meeting notes into structured minutes with decisions, assigned actions, open questions, and next steps.

MIT ★ 28,211 updated 2026-10-16

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add phuryn/pm-skills
/plugin install pm-execution@pm-skills
Open on GitHub

What meeting-notes does

The command accepts a full transcript, rough notes, an audio recap, or several inputs together. It pulls out participants, discussion topics, decisions, action items with owners and deadlines, unresolved questions, useful quotes, and meeting context. The result is saved as Markdown.

Its output is a meeting record with a short overview, a decision list, an action table, discussion highlights, open questions, and next steps. It keeps explored topics separate from conclusions, which helps prevent tentative ideas from being recorded as agreements. An action without an owner is flagged, so those entries need a clear assignment before the notes are shared.

What it helps with

  • turn a transcript into meeting minutes
  • capture decisions from a discussion
  • assign actions to owners and deadlines
  • list unresolved follow-up questions
  • save meeting results as Markdown

Example prompts for the agent

  • Run /meeting-notes on this transcript and create structured meeting minutes.
  • Use /meeting-notes with the meeting notes file and extract decisions, owners, and deadlines.
  • Ask /meeting-notes to produce a short summary, action table, and next steps from these notes.

How to install meeting-notes

1Plugin marketplace

/plugin marketplace add phuryn/pm-skills
/plugin install pm-execution@pm-skills

2Manually: put the files in place

.claude/commands/meeting-notes.md

Call it with /meeting-notes. For all projects use ~/.claude/commands/

Questions about meeting-notes

How do I install meeting-notes in Claude Code?

Add the marketplace with /plugin marketplace add phuryn/pm-skills, install the package with /plugin install pm-execution@pm-skills, then use .claude/commands/meeting-notes.md.

What does meeting-notes do?

It turns a transcript or rough notes into a structured Markdown record. The result covers participants, decisions, action items, open questions, and next steps.

What happens when an action item has no owner?

The command flags it in the output. The task stays in the notes, but its owner still needs to be assigned.

Source text

meeting-notes.md · MIT
---
description: Summarize a meeting transcript into structured notes with decisions, action items, and follow-ups
argument-hint: "<transcript or meeting notes>"
---

# /meeting-notes -- Meeting Summary

Transform a raw meeting transcript or rough notes into clear, structured meeting minutes with decisions captured and action items assigned.

## Invocation

```
/meeting-notes [paste transcript]
/meeting-notes [upload transcript file, audio summary, or notes]
```

## Workflow

### Step 1: Accept the Transcript

Accept in any format:
- Full transcript (from Otter, Fireflies, Google Meet, Zoom, etc.)
- Rough notes taken during the meeting
- Audio summary or meeting recap from a transcription tool
- Multiple inputs (e.g., transcript + the user's own notes)

If the input is sparse, work with what's available and flag gaps.

### Step 2: Extract and Structure

Apply the **summarize-meeting** skill:

Parse the content to identify:
- **Participants**: Who was present (from introductions, speaker labels, or mentions)
- **Topics discussed**: Major agenda items or conversation threads
- **Decisions made**: Explicit agreements or conclusions reached
- **Action items**: Tasks assigned, with owner and deadline if mentioned
- **Open questions**: Unresolved items that need follow-up
- **Key quotes**: Important statements worth preserving verbatim
- **Context**: Meeting type, project, and background

### Step 3: Generate Meeting Summary

```
## Meeting Summary

**Date**: [date if known]
**Participants**: [names/roles]
**Meeting type**: [standup, planning, review, 1:1, stakeholder, etc.]
**Topic**: [primary subject]

### Summary
[3-5 sentence overview of what was discussed and concluded]

### Key Decisions
1. **[Decision]** — [context and rationale]
2. ...

### Action Items
| # | Action | Owner | Deadline | Status |
|---|--------|-------|----------|--------|

### Discussion Highlights
**[Topic 1]**: [key points, different perspectives, conclusion]
**[Topic 2]**: [key points, different perspectives, conclusion]

### Open Questions
- [Question] — needs input from [person/team]

### Next Steps
- [What happens next]
- Next meeting: [if mentioned]
```

Save as markdown.

### Step 4: Offer Follow-ups

- "Want me to **email these notes** to participants?"
- "Should I **create tickets** from the action items?"
- "Want me to **draft a stakeholder update** based on the decisions made?"

## Notes

- Decisions are the most valuable output — make sure every decision is captured clearly
- Action items without owners are useless — if no owner was mentioned, flag it
- Keep the summary concise — people who weren't in the meeting should get the gist in 30 seconds
- If the transcript is very long (60+ min meeting), offer a TL;DR before the full summary
- Distinguish between "discussed" and "decided" — many topics are explored without reaching a conclusion

© Paweł Huryn · MIT · phuryn/pm-skills

Similar slash commands

All slash commands for Writing and docs →

From the same set120

The whole set →
generate-data generate-data generates realistic mock datasets in CSV, JSON, or SQL using Python scripts with custom distributions and constraints. CX Codex +1 ★ 28,211repo stars write-query write-query turns plain language descriptions into SQL queries across BigQuery, PostgreSQL, MySQL and other dialects. Upload a schema or describe your tables, then ask your question. CX Codex +1 ★ 28,211repo stars value-proposition value-proposition maps a product or feature to a six-part template: target user, their job, current friction, your solution, resulting outcome, and why you beat alternatives. CX Codex +1 ★ 28,211repo stars test-scenarios Turns user stories and feature specifications into structured test scenarios covering happy paths, edge cases, and errors. CX Codex +1 ★ 28,211repo stars review-resume review-resume is a Claude Code command that evaluates product manager resumes against best practices and gives three priority improvements with examples. CX Codex +1 ★ 28,211repo stars analyze-cohorts analyze-cohorts runs cohort retention analysis on CSV files or generates SQL frameworks to measure feature adoption. CX Codex +1 ★ 28,211repo stars transform-roadmap transform-roadmap is a Claude Code command that turns a feature list or existing roadmap into an outcome-led plan with success measures and strategic context for product planning. CX Codex +1 ★ 28,211repo stars market-product market-product is a Claude Code command that generates campaign ideas, positioning, value prop copy and product names. It supports launches, rebrands and competitive repositioning. CX Codex +1 ★ 28,211repo stars

Project sponsors

Companies that keep this analytics open