---
name: meeting-to-actions
description: Turns a meeting transcript or messy notes into decisions, owners, deadlines and ready-to-send follow-ups. Use after a meeting, call or when given a transcript or notes.
---

# Meeting to Actions

Input: a transcript, a recording summary, or messy notes. Output: what was decided, who does what by when, what's still open, and the follow-up messages, ready to send.

## Step 1: Read and identify

Read the full input once before writing. Identify:
- **Meeting type**: client call, internal sync, sales call, 1:1, interview, brainstorm.
- **Participants**: names and roles. If the transcript uses "Speaker 1/2", infer names from context ("Thanks, Sara") and say which you inferred.
- **The user**: who in the meeting is the user? If not obvious, assume the person who uploaded it is the host and say so in one line.

## Step 2: Extract (be strict)

**Decisions**: only things that were actually agreed. A suggestion nobody confirmed is not a decision; it goes in Open questions.

**Action items**: each must have:
- **What**: starts with a verb, specific enough that someone else could do it. "Send Sara the revised pricing PDF", not "Follow up on pricing".
- **Owner**: a person. If nobody took it, write `Owner: UNASSIGNED` (these are the ones that get dropped, so flag them).
- **Due**: the date said in the meeting. If none was said, write `Due: not set` and suggest one in brackets.
- **Source**: a short quote or timestamp so the user can verify.

**Open questions**: things raised but not resolved, and who needs to answer them.

**Risks / tension**: disagreement, hesitation, budget concerns, a stakeholder who went quiet. Quote the evidence. Keep it factual, never speculate about people's character.

**Numbers and commitments**: prices, dates, quantities, promises anyone made. These matter most in client and sales calls.

## Step 3: Output

```
# [Meeting name] — [date]
Participants: [names (role)]

## TL;DR
[2-3 sentences: why we met, what we decided, what happens next]

## Decisions
1. [Decision] — "[short quote]"

## Action items
| # | Action | Owner | Due | Source |
|---|--------|-------|-----|--------|

## Open questions
- [Question] → needs answer from [who]

## Numbers & commitments
- [e.g., Quoted $4,500 for phase 1, valid until Oct 31]

## Watch-outs
- [Risk + evidence]
```

## Step 4: Draft the follow-ups

Then write the messages, ready to copy:

1. **Recap email to external participants** (if any): subject line + under 150 words. Thank them in one line, list decisions and their action items with dates, list your action items with dates, confirm the next meeting. No fluff.
2. **Internal message** (Slack/Teams style) for any internal owners: one line per person with their actions.
3. **Calendar suggestion**: if a next meeting was mentioned, propose the title, length and agenda in 3 bullets.

If the `voice-writer` skill or a voice profile is available, write the follow-ups in the user's voice.

## Step 5: Check
- [ ] Every action item starts with a verb and has an owner (or UNASSIGNED).
- [ ] Nothing is listed as a decision unless it was agreed.
- [ ] No invented dates, prices or names.
- [ ] The TL;DR could be read alone and still be useful.

## Rules
- If the transcript is poor quality (missing parts, wrong speaker labels), say so at the top and mark uncertain items with `(?)`.
- Keep personal or sensitive remarks out of the external recap.
- If the input is very long, process it in order and don't skip the last third. Late-meeting decisions are often the important ones.