---
name: meeting-notes-to-actions
description: Turn messy meeting notes into a to-do list you can actually chase. Every row quotes the line it came from, missing owners and deadlines are written as "TBD", and anything still undecided goes under "Open questions" with who needs to answer. Use when someone pastes meeting notes, a transcript or a recap and asks for action items, to-dos or a follow-up list.
---

# Meeting notes → a traceable to-do list

Goal: whoever reads the table can trace every row back to the notes, and nothing in it was quietly made up.

## When to use

- Someone pastes notes, a transcript or a voice-to-text dump and asks to "clean it up", "list the to-dos" or "pull out action items"
- The notes contain vague timing ("before next week", "Friday"), unowned work, or decisions that are still open

Not a fit for formal minutes that need the full discussion, since this keeps only tasks and open questions.

## Ask first (only if the notes don't say, and only once)

1. Who will read the list and what will they do with it ("the team lead uses it to chase progress")
2. The year of the meeting, if the notes only give month and day. Do not add a year yourself

If there's no answer, assume the reader is whoever chases progress and leave the year out.

## Steps

1. Read each line and sort it: **assigned work** (someone said they'd do it), **unowned work**, **open decisions** (dates, budgets, whether to do something)
2. Assigned and unowned work go in the task table. Open decisions are **not** tasks: list them under "Open questions"
3. The "Source line" column quotes the note word for word (shorten if needed, never reword the meaning)
4. Owner and deadline: copy them if the notes state them. **If not, write "TBD".** Do not borrow another date from the notes (e.g. do not turn "next meeting Oct 28" into a deadline)
5. You may convert vague timing ("next Friday", "before Wednesday") into a date, but say how, e.g. "Oct 31 (notes say 'Friday', counted from the Oct 21 meeting)"
6. **Do not use your own idea of today's date** to mark anything overdue, "tomorrow" or "this week". Every date comes from the notes
7. End with a self-check that lists everything you inferred or converted that the notes don't state directly. If nothing, write "None"

## Output format

```markdown
## Tasks

| Task | Owner | Deadline | Source line |
|---|---|---|---|
| … | … | TBD | "…" |

## Open questions

| Question | Who answers | Source line |
|---|---|---|
| … | … | "…" |

**Self-check:** …
```

No emojis, no "recommendations" section, no reminders the notes don't contain.

## Limits

- The self-check can miss its own guesses. In testing, Claude Haiku 4.5 converted a date and still said it had inferred nothing. Check the deadline column against the quotes yourself
- "Next Friday" is ambiguous (this week's Friday or the following one). Ask the person who said it
- Short or very casual notes produce a lot of "TBD". That's the notes, not the table

## Install

- Claude Code: put this folder in `~/.claude/skills/meeting-notes-to-actions/` (all projects) or a project's `.claude/skills/`
- Claude apps: upload the folder as a zip in the Skills settings
- ChatGPT and others: paste the Steps and Output format sections into custom instructions, or in front of your notes. Untested there