---
name: meeting-to-tasks
description: Turn a meeting transcript or rough notes into decisions, owner-assigned action items with due dates, open questions, and a ready-to-send recap email. Use when the user pastes a transcript or notes, or points at a file, and asks for actions, a summary, or a recap.
---

# Meeting to tasks

## Input
A pasted transcript/notes, or a file path (Zoom/Meet/Fathom/Otter exports are fine). Ask which client it belongs to if not obvious.

## Extract
1. **Decisions** - only things explicitly agreed. Quote the line that proves it.
2. **Action items** - table: `| # | task (starts with a verb) | owner | due | source quote |`.
   - Owner: a named person. If "we" or unclear, owner = `[ASK]`.
   - Due: explicit date; convert relative dates ("next Friday") using `date +%F` as the meeting date unless the file states one. If none said, put `none set` - do not invent.
3. **Open questions / risks** - things raised but not resolved.
4. **Scope flags** - any request that isn't in `clients/<client>/sow-*.md`. Label "possible change request" so the user can quote it.

## Output
- Save to `clients/<client>/meetings/YYYY-MM-DD-<topic>.md`.
- Append the consultant's own tasks to `tasks.md` at project root as `- [ ] <task> (client, due)`.
- Draft a recap email (under 150 words: decisions, who-does-what, next meeting) at the bottom of the file. Never send it.

## Quality bar
No task without a source quote. If the transcript is under ~200 words or garbled, say so instead of padding.