Personal Ops
Meeting Transcript Action Miner
Turn messy meeting records into owned next actions without inventing commitments.
Use when
A meeting transcript, chat log, or call note contains promises and decisions that could disappear into the transcript graveyard.
Beginnerdifficulty
Personal Opscategory
Mia daily expansionsource
Cadence
After recorded meetings or dense calls
Verification
Decisions, commitments, owners, due dates, and unresolved questions are captured with source evidence; no external follow-up is sent without approval.
Structured loop spec
| Field | Value |
|---|---|
| Name | Meeting Transcript Action Miner |
| Category | Personal Ops |
| Trigger | After recorded meetings or dense calls |
| Objective | Turn messy meeting records into owned next actions without inventing commitments. |
| Allowed inputs | Relevant files, source notes, logs, tests, screenshots, metrics, or task state for this loop |
| Allowed actions | Collect the transcript, chat, agenda, attendee list, and any shared docs for the meeting window.; Extract explicit decisions, promised follow-ups, open questions, deadlines, and named owners with short source quotes or timestamps.; Separate confirmed commitments from suggestions, brainstorms, and unclear language that needs human review.; Draft task updates, meeting notes, or follow-up emails in the user's voice, but keep external sends approval-gated.; Stop when every actionable item is captured, assigned, deferred for review, or explicitly marked no-action with evidence. |
| Verification | Decisions, commitments, owners, due dates, and unresolved questions are captured with source evidence; no external follow-up is sent without approval. |
| Stop condition | Stop when the verifier passes, the budget is exhausted, no progress is made, a blocker appears, or approval is required. |
| Budget | Set a time, turn, token, retry, file, or dollar cap before running the loop. |
| Approval boundary | Human approval required before publishing, sending, deleting, spending, changing accounts, touching production, or making reputational/legal/financial commitments. |
| Safe output | Draft, report, checklist, table, or approval-gated recommendation |
| Works with | Claude, ChatGPT, Gemini, any tool-using AI assistant |
Steps
- Collect the transcript, chat, agenda, attendee list, and any shared docs for the meeting window.
- Extract explicit decisions, promised follow-ups, open questions, deadlines, and named owners with short source quotes or timestamps.
- Separate confirmed commitments from suggestions, brainstorms, and unclear language that needs human review.
- Draft task updates, meeting notes, or follow-up emails in the user's voice, but keep external sends approval-gated.
- Stop when every actionable item is captured, assigned, deferred for review, or explicitly marked no-action with evidence.
Prompt
Run the Meeting Transcript Action Miner loop. Given a transcript, chat log, meeting note, or recording summary, extract decisions, commitments, owners, due dates, open questions, and follow-ups with source quotes or timestamps. Distinguish confirmed commitments from suggestions and unclear language. Draft tasks, notes, or follow-up messages, but do not send external messages or commit the user without approval. Return the action register, review queue, and evidence map.Run in Claude Code
Paste this into Claude Code (or any tool-using agent) to run the loop bounded: one change per round, the same verification every round, durable state files, and explicit stop conditions.
Run the "Meeting Transcript Action Miner" loop from AI Loop Library (https://ailooplibrary.com/loops/meeting-transcript-action-miner/) as a bounded loop.
Goal: Turn messy meeting records into owned next actions without inventing commitments.
Rules: one change per round; run the same verification every round (Decisions, commitments, owners, due dates, and unresolved questions are captured with source evidence; no external follow-up is sent without approval.); append each round to docs/loops/meeting-transcript-action-miner/progress.md and update docs/loops/meeting-transcript-action-miner/state.json; stop on verifier pass, 8 rounds, 3 consecutive failed verifications, no progress, a blocker, or anything needing human approval (money, production, outbound, deletion). Finish with a proof report: rounds used, changes made, verification output, remaining risk, and the next human decision.