← Blog · 2026-10-14

Stop Losing Action Items: Turn Any Meeting Transcript Into Owned, Dated Tasks with Claude Code

Most AI meeting summaries fail the same way: they're confident, tidy, and partly invented. "John will send the deck by Friday" when nobody said Friday. For a consultant, an invented commitment is worse than no summary: it ends up in a client email.

Here's a method that fixes it, using a Claude Code skill with one non-negotiable rule: no task without a source quote.

The four things worth extracting

1. Decisions: only what was explicitly agreed, with the line that proves it.
2. Action items: verb-first task, a named owner, a due date, and the quote it came from.
3. Open questions: raised but not resolved.
4. Scope flags: anything the client asked for that isn't in the signed scope. These are your future change requests — the most valuable thing in the transcript, and almost every summary tool ignores them.

Rules that stop hallucinated tasks

• Owner must be a named person. "We'll look into it" becomes owner [ASK], not you by default.
• Dates only if said. Relative dates ("next Friday") are converted using the meeting date. If no date was said, write none set.
• Quote or it didn't happen. Every row cites the transcript line. You can verify the whole table in 30 seconds.
• Refuse thin input. If the transcript is under ~200 words or garbled, say so instead of padding.

The skill

Save as .claude/skills/meeting-to-tasks/SKILL.md in your project:

---
name: meeting-to-tasks
description: Turn a meeting transcript or notes into decisions, owner-assigned action items with due dates, open questions, and a recap email. Use when the user pastes a transcript or asks for actions or a recap.
---
# Meeting to tasks
Extract: Decisions (quote the line), Action items table
| # | task (verb-first) | owner | due | source quote |,
Open questions, Scope flags (requests not in clients/<client>/sow-*.md).
Owner unclear -> [ASK]. No stated date -> "none set". Convert relative dates
from the meeting date. No task without a source quote.
Save to clients/<client>/meetings/YYYY-MM-DD-<topic>.md, append my own tasks to
tasks.md, and draft a recap email under 150 words. Never send it.

Running it

Export the transcript from Zoom, Meet, Fathom or Otter, drag the file into Claude Code, and say "turn this into tasks for Acme". You get:

…plus a scope flag: "Could you also look at our offboarding?" is not in the SOW, so treat it as a possible change request.

Why the scope flag matters

Unbilled scope creep is the quiet margin killer in solo consulting. Catching "could you also…" the same day lets you reply with a one-line change quote while the request is fresh, instead of discovering in week six that you've been doing it for free.

Try the skill yourself

This skill ships in a free three-skill folder (with invoice-chase and client-follow-up):

Free 3-skill sample
More free Claude Code skills, hooks and workflows from around the web:

Solo Stack Kits Directory
If you want the full consultant back office (proposals, SOWs, weekly review, discovery prep, case studies) plus safety hooks:

Solo Consultant Kit
Disclosure: I make Solo Stack Kits. The sample is free; paid kits are optional.

Not affiliated with Anthropic; "Claude" is a trademark of Anthropic.