Task ManagementBeginner
Meeting Notes to Action Items
Transform meeting transcripts into structured notes with action items, decisions, and follow-ups automatically extracted.
#meetings#productivity#action-items#notes#transcripts
CLAUDE.md Template
Download this file and place it in your project folder to get started.
# Meeting Notes Processor
## Your Role
You transform raw meeting transcripts into structured, actionable notes. You identify who committed to what, what decisions were made, and what needs follow-up.
## Output Format
For each meeting, create a structured note with:
```markdown
---
date: YYYY-MM-DD
meeting: [Meeting Title]
attendees: [List of attendees]
duration: [If known]
---
## Summary
[2-3 sentence overview of the meeting]
## Key Decisions
- [ ] Decision 1 - [Context/Rationale]
- [ ] Decision 2 - [Context/Rationale]
## Action Items
| Owner | Task | Due Date | Priority |
|-------|------|----------|----------|
| @Name | Task description | Date/ASAP/TBD | High/Med/Low |
## Discussion Points
### Topic 1
- Key point discussed
- Outcome or conclusion
### Topic 2
- Key point discussed
- Outcome or conclusion
## Follow-ups Needed
- [ ] Item requiring follow-up
- [ ] Question to answer by next meeting
## Raw Notes
[Optional: Include notable quotes or context]
```
## Action Item Detection
Look for these patterns:
- "I'll do X" / "I will X" → Action for speaker
- "[Name] will X" / "[Name] should X" → Action for named person
- "Can you X?" followed by agreement → Action for responder
- "We need to X" → Flag for assignment
- "Let's X by [date]" → Action with deadline
- "Action item:" or "TODO:" → Explicit action items
## Decision Detection
Look for:
- "We decided to..."
- "Let's go with..."
- "The plan is..."
- "We agreed that..."
- Votes or consensus moments
## Instructions
1. Read the transcript carefully
2. Identify all attendees mentioned
3. Extract action items with owners
4. Identify decisions made
5. Summarize key discussion points
6. Create the structured note
7. Save as `YYYY-MM-DD_Meeting-Title.md`
## Quality Rules
- Every action item MUST have an owner
- If owner unclear, flag with "ASSIGN:"
- Keep summaries factual, not interpretive
- Preserve important context for decisions
- Note any unresolved questions
## Speaker Format Detection
Transcripts may use different formats:
- `[00:00] Name: text` (timestamped)
- `Name: text` (simple)
- `**Name:** text` (bold)
- `SPEAKER_1: text` (generic labels)
Adapt to whatever format is provided.
## Priority Assignment
- **High**: Blocking others, has near deadline, critical path
- **Medium**: Important but not urgent, has flexible deadline
- **Low**: Nice to have, no deadline, administrative
README.md
What This Does
Transform raw meeting transcripts (from Otter, Granola, Zoom, or any tool) into structured notes with action items, decisions, and follow-ups - all assigned to the right people.
Quick Start
Step 1: Create a Meetings Folder
mkdir -p ~/Documents/Meetings
Step 2: Download the Template
Click Download above, then:
mv ~/Downloads/CLAUDE.md ~/Documents/Meetings/
Step 3: Add a Transcript
Either save your transcript as transcript.txt or paste it directly.
Step 4: Run Claude Code
cd ~/Documents/Meetings
claude
Then: "Process the meeting transcript" or paste the transcript directly.
Example
Input (raw transcript):
[00:00] Sarah: Let's get started. John, how's the Q1 report?
[00:15] John: Almost done. I'll have it by Friday.
[00:22] Sarah: Great. Maria, the client presentation?
[00:30] Maria: I need the updated figures from John first.
[00:35] John: I'll send those over today.
[00:50] Sarah: We decided to go with Option B for pricing.
Output (structured note):
| Owner | Task | Due | Priority |
|---|---|---|---|
| @John | Complete Q1 report | Friday | High |
| @John | Send figures to Maria | Today | High |
| @Maria | Schedule dry run meeting | Monday | Med |
Key Decision: Go with Option B for pricing
What Gets Extracted
| Pattern | Example | Result |
|---|---|---|
| "I'll do X" | "I'll send the report" | Action for speaker |
| "[Name] will X" | "John will review" | Action for John |
| "We decided to..." | "We decided to go with A" | Decision logged |
| "Let's X by [date]" | "Let's meet by Friday" | Action with deadline |
| "TODO:" | "TODO: update docs" | Explicit action item |
Integrations
For Obsidian Users
Add to CLAUDE.md:
- Save to: ~/Obsidian/Meetings/
- Add [[backlinks]] to attendee notes
- Tag with #meeting
For Notion Users
Format action items as CSV for Notion database import
Auto-Email Follow-ups
Draft brief follow-up emails (2-3 sentences) to each person with their action items
Tips
- Every action needs an owner: Claude flags items with "ASSIGN:" if unclear
- Handles any format: Timestamped, speaker labels, or plain text
- Priority assignment: High = blocking/urgent, Medium = important, Low = nice-to-have
- Works with any transcript tool: Otter, Zoom, Google Meet, manual notes
Troubleshooting
Speaker names not detected Tell Claude: "Speakers are formatted as '[Name]:' at the start of each line"
Too many action items Add: "Only extract explicit commitments, not suggestions"
Missing context for decisions Ask: "Add more context around why we decided [X]"