process-meeting-transcript

# Process Meeting Transcript

## Overview

Process raw meeting transcripts into well-structured Obsidian notes with YAML frontmatter, extracted action items, meeting summary, and properly formatted transcript sections.

## When to Use This Skill

Use this skill when:
- User provides a raw meeting transcript (typically from Granola)
- User asks to "process a meeting transcript" or "format meeting notes"
- User points to a file containing an unprocessed transcript
- User pastes transcript content directly into the conversation

## Workflow

### Step 1: Read the Transcript

If the transcript is in a file, read the entire contents. If the user pasted the transcript directly, use that content.

### Step 2: Extract Action Items

Carefully review the entire transcript to identify all action items, tasks, and commitments. Look for:
- Explicit commitments: "I'll do X", "Alex will review Y"
- Assigned tasks: "Nathan and Damian should schedule..."
- Follow-up items: "We need to...", "Let's make sure to..."
- Decisions requiring action: "We should deploy X before Y"

Format action items as:
- Bulleted list under `# Action Items` heading
- Use **bold** for person names when specific people are assigned
- Include context for what needs to be done and why
- Order by priority/importance when evident from discussion

Example format:
```markdown
# Action Items

- **Alice & Bob**: Review the new feature implementation next week and provide feedback
- **Charlie & Dana**: Schedule a knowledge transfer session on the payment service architecture
- **Eve**: Discuss deployment timeline with the infrastructure team
```

### Step 3: Create Meeting Summary

Write a comprehensive but concise summary that captures:
- Main topics discussed
- Key decisions made
- Technical architecture or approach agreed upon
- Timeline and next steps
- Important context or constraints

Structure the summary with:
- Opening paragraph: High-level overview of what was discussed and main outcome
- Subsections (using