# Pmstudio Meeting Notes

Generate structured meeting notes from transcripts or pasted text.

- Repository: https://github.com/coco-research/coco (797 stars)
- Category: AI and agents
- License: see repository
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add coco-research/coco --skill pmstudio-meeting-notes -g -a claude-code -y`
Codex: `npx skills add coco-research/coco --skill pmstudio-meeting-notes -g -a codex -y`
Cursor: `npx skills add coco-research/coco --skill pmstudio-meeting-notes -g -a cursor -y`
Gemini CLI: `npx skills add coco-research/coco --skill pmstudio-meeting-notes -g -a gemini-cli -y`

## Description

Generate structured meeting notes from transcripts or pasted text. Use when someone says "meeting notes", "process this transcript", "summarize this call", "notes from today's meeting", or pastes/references a meeting transcript. Auto-enriches attendees from stakeholder directory, routes output to correct project subfolder, flags downstream artifact impacts (PRD, deck, architecture), and proposes CLAUDE.local.md updates. Produces date-first Markdown files.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Meeting Notes, Transcript-to-Artifact Generator

## Purpose

Transforms raw meeting transcripts (pasted text, audio transcription output, or file references) into structured, stakeholder-enriched meeting notes. Not generic summaries, these cross-reference project context, known stakeholders, and existing artifacts to produce notes that integrate into the project's documentation ecosystem.

## Process

### Step 1: Determine Input Source

From user request:

| Input | How to Handle |
|-------|---------------|
| Transcript pasted in chat | Process directly |
| File path provided | Read the file |
| `/pmstudio-meeting-notes <path>` | Read file at path |
| `/pmstudio-meeting-notes <path> <output-dir>` | Read file, write to specified directory |
| No transcript provided | Ask: "Paste the transcript or provide a file path" |

### Step 2: Read Project Context

**Always read (skip any that don't exist):**

1. **`CLAUDE.local.md`**, critical for:
   - Folder structure & routing guide (determines where to save notes)
   - Recent Changes (avoid duplicating known information)
   - Key Decisions (cross-reference decisions mentioned in transcript)
   - Open Questions (check if any were answered in this meeting)
   - File naming conventions

2. **Stakeholder Directory**, scan for:
   - `**/Stakeholder*.xlsx` or `**/Stakeholder*.md`
   - `**/Data/Stakeholder*`
   - Known stakeholder names, roles, emails, groups

3. **Recent meeting notes**, read the last 1-2 meeting note files to:
   - Match format and depth conventions
   - Identify follow-ups from previous meetings
   - Detect recurring topics

4. **PRD files**, scan for `**/*PRD*.html` or `**/*PRD*.md` to:
   - Know current PRD version
   - Identify if meeting content impacts requirements

### Step 3: Extract & Enrich

Process the transcript to extract:

The rest: https://github.com/coco-research/coco/blob/HEAD/skills/meeting-notes/SKILL.md