meeting-notes

Quick Start

What to provide: Raw meeting content in any format.

/meeting-notes                           → I'll ask for your content
/meeting-notes [paste transcript]        → Process immediately
/meeting-notes [paste notes] --minimal   → Quick-capture format
/meeting-notes [paste notes] --slack     → Slack-friendly format

Accepted inputs: Zoom/Otter/Grain transcripts, bullet-point notes, voice memo dictation, Slack threads, email chains, or just "tell me what happened."

What you get: Structured notes with decisions, action items (with owners and dates), key insights, open questions, and next steps. Saved to thoughts/shared/product/meeting-notes/[date]-[topic].md.

Time: 2-5 minutes per meeting.

Input Length Guidance

| Transcript Length | Approach | | -------------------------------- | -------------------------------------------------------------------------------------------------------------- | | < 30 min (under ~5,000 words) | Process normally in one pass | | 30-60 min (~5,000-10,000 words) | Process normally, may compress detail | | 60-90 min (~10,000-15,000 words) | Split into logical segments (by topic or agenda item) and process each | | 90+ min (15,000+ words) | Ask the PM to provide the transcript in chunks, or identify the most important 30-min segment to process first |

For very long transcripts: "This is a long transcript. I can process it all, but the output will be more accurate if we focus. Which approach do you prefer?

1. Full processing - I'll cover everything but may compress less important sections
2. Key segments only - Tell me which agenda items or topics matter most
3. Chunked processing - Paste the transcript in 2-3 parts and I'll process each"

/meeting-notes - Transform Meeting Transcripts Into Action

When the PM types /meeting-notes, process raw meeting notes, transcripts, or recordings and extract structured action items, decisions, and key insights.

Context Routing Logic (Internal - for Claude)

Automatic Context Checks: When this skill is invoked, immediately check:

| Source | Files/Folders | Search Terms | What to Extract | | -------------------- | ---------------------------------- | -------------------------------- | ------------------------------------------ | | Related PRDs | thoughts/shared/pm/prds/.md | feature from meeting | PRD context, decisions already made | | Stakeholder Profiles | Stakeholder templates | attendees from meeting | Communication style, preferences, concerns | | Strategy | thoughts/shared/pm/frameworks/.md | feature or decision from meeting | Strategic alignment context | | Previous Meetings | thoughts/shared/product/meeting-notes/*.md | topic from this meeting | Historical context, related decisions | | Action Items | Previous meeting notes | same owners, same topics | Recurring blockers or items |

Context Priority:

1. Stakeholder context and communication style FIRST
2. Related PRDs and decisions SECOND
3. Strategic context THIRD
4. Historical meeting context FOURTH

Cross-Skill Links:

• If customer interview → Auto-flag for /user-research-synthesis if > 3 customer conversations
• If decision about feature → Update related PRD in /prd-draft
• If action items about research → Link to /interview-guide or /user-research-synthesis
• If strategy discussion → Update /write-prod-strategy context

Step 0: Understanding Meeting Context

Before processing, let me check if there's relevant context...

Checking:

• thoughts/shared/product/meeting-notes/ for any previous meetings on this topic
• Stakeholder profiles for communication style of attendees
• thoughts/shared/pm/prds/ for related feature context
• thoughts/shared/pm/frameworks/ for strategic alignment

Based on what I find, I'll show you:

Meeting Context

Type: [Customer interview / Stakeholder review / Team planning / 1:1 / Design review / Engineering sync / other?]

Topic: [Feature or area being discussed]

Key Participants:

• [Who was there and their role]
• [Communication style from stakeholder profiles: what matters to them?]

Related Context:

• [PRDs: any feature PRDs this relates to?]
• [Previous decisions: any decisions already made on this topic?]
• [Strategic fit: how does this relate to Q# goals?]

PM-Specific Diagnosis Questions

1. Decision Type: Is this a decision-making meeting or information-sharing?
2. Stakeholders: Who are the decision-makers vs. advisors?
3. Dependencies: What other meetings or decisions does this depend on?
4. Urgency: Are there time-sensitive decisions or deadlines?
5. Follow-up Needed: What needs to happen before next steps?

When to Use

• After any customer interview, stakeholder meeting, or team sync
• Processing a day's worth of back-to-back meetings
• Converting rambling voice memos into clear next steps
• Extracting decisions and action items from Slack threads
• Creating meeting summaries for people who couldn't attend

How It Works

This is a 2-step process:

Step 1: Upload or Paste Your Raw Content

Step 2: Get Structured Output in Your Format

Step 1: Upload Raw Content

When the PM types /meeting-notes, start with:

Let's transform your meeting notes into structured action items.

**What do you have?**

You can give me:
- Raw transcript (from Zoom, Grain, transcription tool, Google Meet)
- Your quick notes (bullet points, fragments, whatever you captured)
- Voice memo or dictation
- Slack thread or email chain
- Just talk it out - tell me what happened in the meeting

**What kind of meeting was this?**
- Customer interview
- Stakeholder review
- Team planning session
- 1:1 with manager
- Design review
- Engineering sync
- Other: [specify]

**Who was there?**
[Names help me assign action items correctly]

Paste or upload your content, and I'll structure it for you.

What I'm Looking For

As you share, I'll automatically extract:

✅ Action items - Clear next steps with owners ✅ Decisions made - What was decided and why ✅ Open questions - Unresolved issues that need follow-up ✅ Key insights - Important context or quotes ✅ Blockers - Things preventing progress ✅ Next steps - What happens next and when

Step 2: Structured Output

Once I have your content, I'll say:

Got it. I'm processing your [meeting type] notes.

I'll create a structured summary with:
- Action items (with owners and due dates)
- Decisions made
- Key insights
- Open questions
- Next steps

Output format: [Standard / Detailed / Minimal]
(I'll use your preferred writing style from thoughts/shared/pm/context/writing-style-*.md)

Processing now...

Standard Format Output

# Meeting Notes: [Meeting Title/Topic]

**Date:** [Date]
**Attendees:** [Names]
**Meeting Type:** [Customer Interview / Stakeholder Review / etc.]
**Duration:** [Time]

---

## Summary

[2-3 sentence overview of what was discussed and the main outcome]

---

## Decisions Made

1. **[Decision]**
   - **Why:** [Rationale]
   - **Who decided:** [Name]
   - **Impact:** [What this affects]

2. **[Decision]**
   - **Why:** [Rationale]
   - **Who decided:** [Name]
   - **Impact:** [What this affects]

---

## Action Items

| Task                   | Owner   | Due Date | Priority | Status         |
| ---------------------- | ------- | ---