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: