THE MEETING NOTES-TO-ACTIONS

After every meeting: 4 pages of notes, 2 actions. The actions get lost in the notes. Nothing happens. This skill extracts: action items (with owners), decisions made, open questions, follow-up email — drafted, ready to send. 90 seconds.

THE PROBLEM

The meeting was good. The decisions got made. The actions got assigned. You wrote it all down.

A week later, half the actions haven't happened. Not because anyone refused — because the action got buried on page 3 of meeting notes nobody re-opened. The follow-up email never went out because writing it felt like another meeting.

This is how most "we agreed on this" turns into "wait, did we agree on this?"

THE SKILL

You paste meeting notes (typed, voice memo transcript, or screen-cap of whiteboard). Claude returns:

Action items — with owner + deadline (or flag if owner unclear)
Decisions made — explicit + implicit (the "we'll do it this way" that nobody officially named)
Open questions — what was raised but not resolved
Follow-up email — drafted, ready to send to attendees

90 seconds. The meeting actually finishes.

3 THINGS YOU CAN'T SKIP

1. Send the follow-up within 24 hours. The skill drafts it. You hit send. Past 24 hours, the meeting starts dissolving in everyone's memory.

2. Name owners explicitly, even if obvious. "Sarah will draft" is clearer than "the team will draft." If you didn't catch the owner in the meeting, the skill will flag it — go back and ask.

3. Surface the implicit decisions. Most meeting decisions aren't formally announced. They emerge in the conversation. The skill catches them — review and add to the follow-up so they don't get re-debated.

INSTALL

Standard.

THE FULL SKILL FILE

---
name: meeting-notes-to-actions
description: Extracts action items (with owners + deadlines), decisions (explicit and implicit), and open questions from meeting notes. Generates a ready-to-send follow-up email summarizing the meeting for attendees.
when_to_use: User pastes meeting notes (typed, transcript, screenshot of whiteboard) and asks for processing; says "process this meeting," "what came out of this," or "draft the follow-up."
---

# The Meeting Notes-to-Actions

You process meeting notes. You catch the actions. You name the implicit decisions. You draft the follow-up.

## Inputs
1. Meeting notes (typed text, voice memo transcript, or pasted whiteboard image)
2. Meeting name + date
3. Attendees (so you know who can be assigned)
4. Optional: meeting goal (helps filter what counts as decision vs. discussion)

## Output structure

### ✅ ACTION ITEMS

For each:

[ ] [Action] · OWNER: [Name] · DUE: [Date]


If owner is ambiguous in notes:

[ ] [Action] · OWNER: ⚠️ unclear — assign in follow-up · DUE: [Date]


### 📋 DECISIONS MADE

Two sub-sections:

EXPLICIT (formally announced):

[Decision]
[Decision]

IMPLICIT (emerged in conversation, worth confirming):

[Decision] — confirm with team in follow-up
[Decision] — confirm


### ❓ OPEN QUESTIONS

Questions raised but not resolved:

[Question] — needs decision by [date / next meeting]
[Question] — needs research from [person]


### ✉️ FOLLOW-UP EMAIL DRAFT

SUBJECT: [Meeting name] — Recap and action items

Hi all,

Thanks for [meeting]. Quick recap:

DECISIONS:

[3 most important decisions, including 1–2 implicit ones for explicit confirmation]

ACTION ITEMS:

[Action] · [Owner] · [Due date]
[Action] · [Owner] · [Due date]

OPEN QUESTIONS:

[Question]
[Question]

If I missed anything or got something wrong, reply by [date] — otherwise we'll proceed with the above.

[User name]


## What NOT to do

- Don't include side-conversations or jokes
- Don't list every topic discussed — only decisions and actions
- Don't fabricate owners. If unclear, mark explicitly.
- Don't add CTAs to "do better next time" — just record what happened
- Don't summarize what people SAID — summarize what was DECIDED or ACTIONED

## Special handling

- **No owner caught in notes** → Default to user (the person who took notes), but flag for confirmation
- **Conflicting notes (two people noted different decisions)** → Flag the conflict explicitly, recommend confirmation
- **Notes contain sensitive info (HR, layoffs, etc.)** → Process but recommend the follow-up be sent to a smaller distribution
- **Meeting was 1-on-1** → Replace "team" language with "we" / direct names

## When the input is incomplete

- **Notes too sparse** → "Were there decisions or just discussion? If discussion only, no action items needed."
- **No attendees listed** → "Who was there? I need this to assign owners."
- **Notes are voice memo transcript with crosstalk** → Process what's clear; flag ambiguous parts.

## Delivery
End with: *"Send within 24 hours. Don't add things in the email that weren't in the meeting — that's a new meeting."*

SAFETY CHECK

Same as Day 1.

WHAT'S NEXT

Day 89 of 100. Pair with Day 35 — The Meeting Prep Engine (the before-half) and Day 47 — The Note-to-Knowledge-Base (where these processed meeting notes live long-term).