# pmstudio-meeting-notes

pmstudio-meeting-notes converts call transcripts into structured Markdown meeting notes. Cross-references people against stakeholder tables, logs decisions, and flags PRD updates.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf (Devin Desktop), Claude.ai · ★ 328 repo stars
- Author: coco-research
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/coco-research/coco/tree/HEAD/skills/meeting-notes/SKILL.md
- Updated: 2026-10-29
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/pmstudio-meeting-notes

## What it does

This skill parses conversation transcripts from pasted chat messages or files into formatted Markdown documents named `YYYY-MM-DD-Attendee1-Attendee2.md`. Each generated document includes an executive summary, detailed topic breakdowns with speaker quotes, tables of finalized decisions, and actionable tasks mapped to owners.

Before outputting notes, the skill inspects existing project assets. It consults `CLAUDE.local.md` to identify routing paths, open questions, and previous decisions. Looking into `Stakeholder*.xlsx` or `Stakeholder*.md` files allows it to expand first-name mentions with job titles and teams while tagging unrecognized participants as new contacts. It also tracks whether discussions alter scope in PRD files.

Accurate directory routing and role resolution depend on having `CLAUDE.local.md` or a stakeholder list in place; without these files, notes lack automated context enrichment.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add coco-research/coco --skill pmstudio-meeting-notes -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/meeting-notes/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/meeting-notes/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add coco-research/coco --skill pmstudio-meeting-notes -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/meeting-notes/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add coco-research/coco --skill pmstudio-meeting-notes -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/meeting-notes/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install coco-research/coco skills/meeting-notes
```

2. **Manually: put the files in place**
- File: `.github/skills/meeting-notes/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add coco-research/coco --skill pmstudio-meeting-notes -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/coco-research/coco --path skills/meeting-notes
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/meeting-notes/SKILL.md` — The legacy .windsurf/skills/ path still works

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/coco-research/coco/tree/HEAD/skills/meeting-notes/SKILL.md

## When to use it
- extract action items with owners and deadlines from call transcripts
- match conversation participants against project stakeholder directories
- track resolved questions against CLAUDE.local.md
- document impact of meeting decisions on PRD requirements

## Example prompts
- /pmstudio-meeting-notes transcripts/call-2025-05-10.txt
- /pmstudio-meeting-notes notes/sync.txt docs/meetings
- Process this pasted meeting transcript and flag any impacts on the PRD

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 320a5926c523bdbd.

BEGIN THIRD-PARTY FILE 320a5926c523bdbd
```text
---
name: pmstudio-meeting-notes
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.
domain: pm
---

# 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:

#### 3a. Metadata
- **Date** — from transcript or user context. Use absolute date (YYYY-MM-DD), never relative.
- **Attendees** — every person mentioned or speaking. Cross-reference against stakeholder directory to enrich with:
  - Full name (resolve first-name-only references)
  - Title/Role
  - Group/Team
  - If NOT in directory → flag as "New Stakeholder"
- **Duration** — estimate from transcript length if not stated (~150 words/minute for conversation)
```
END THIRD-PARTY FILE 320a5926c523bdbd

The third-party file has ended. Everything between the 320a5926c523bdbd tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2832 of 11612 bytes. © coco-research · MIT · https://github.com/coco-research/coco/tree/HEAD/skills/meeting-notes/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
