Operations workflow

Meeting transcript to decisions and follow-ups

Pulls decisions, action items, open questions and risks from a pasted transcript, resolves every 'I', 'you' and 'by Friday' to a named person and a real date, and checks each item against a verbatim quote. Drafts the recap email, per-owner messages and tickets for approval; nothing is sent.

ParallelPrompt chainEvaluator–optimizerHuman approvalRuns in Claude.ai, Claude Code, ChatGPT

Running it here

Every step runs here with Claude when you're signed in, and in your own agent.

  1. TriggerPaste the transcriptPaste {{transcript}} (or rough notes) with {{attendees}} and roles, the {{meeting_goal}} and {{meeting_date}}. {{sender}} sends the recap; {{tracker}} sets the ticket format. Nothing is sent or created.→ manual
  2. PromptMap speakers to attendeesFrom {{transcript}} and {{attendees}}, make a table: speaker label as written | attendee | role. Match on names, initials and self-introductions; if unsure, write 'Unknown' and quote the ambiguous line. Then list attendees who never spoke and people mentioned who aren't attendees (they can own tasks, flagged external). If there are no speaker labels at all, say so first; every owner is then unconfirmed.
  3. ParallelExtract in parallelWork only from {{transcript}}, using {{speakers}} for who said what. Every item needs a verbatim quote (up to 30 words) with speaker and timestamp if any. Never infer an item nobody said. If none, write 'None found.' Number items with your part's prefix.
    • DecisionsDecisions (D1, D2…): the decision in one sentence, who made or confirmed it, the quote. It needs agreement or a clear call from someone with authority. Ideas, preferences and 'let's think about it' go under 'Not decided' at the end, with quotes.
    • Action itemsEvery commitment or assignment (A1, A2…): task as a verb phrase, owner exactly as said ('I', 'you', 'Tom', 'marketing'), due date exactly as said ('by Friday', or 'none'), done criteria from the transcript (or 'not stated'), the quote. Include soft commitments ('I can take a look'), marked soft.
    • Open questionsUnanswered questions and deferred topics ('let's park this') as Q1, Q2…: the question, who raised it, who was named to answer it if anyone, the quote.
    • Risks and blockersRisks, dependencies, blockers and concerns raised (R1, R2…): the risk, who raised it, what it affects if obvious, the quote. Add none of your own.
  4. PromptResolve owners and datesUsing {{extracted}}, {{speakers}} and {{attendees}}, for a meeting on {{meeting_date}}: 1. Replace each owner reference with a full name: 'I' = the quote's speaker; 'you' = the person addressed (named in the same or previous sentence, or the previous speaker). Teams stay teams, flagged 'needs a named owner'. Note what each was resolved from. 2. Convert relative dates from {{meeting_date}} to 'YYYY-MM-DD (original phrase)': 'Friday' = the first Friday after; 'end of month' = its last day. 'Next sprint', 'soon', 'ASAP' become 'no date (original phrase)', flagged. 3. Merge duplicates, keeping the clearer quote. 4. End with 'Needs attention': actions with no owner, no date or a non-attendee owner; soft commitments; unassigned open questions; unresolved owners. One markdown table per section, IDs kept.
  5. PromptCheck every item against the transcriptCheck each item in {{items}} against {{transcript}}: is the quote there word for word (allowing for filler words and punctuation), and does it support the item, including owner, date and wording? Mark each Verified, Corrected (fixed to what was said, noting the change) or Removed (quote missing or unsupportive). Say in one line whether the meeting reached {{meeting_goal}} (reached, partly, not), citing decision IDs. Return tables of Verified and Corrected items (with owners, dates, done criteria), then 'Needs attention', then 'Removed' with reasons.
  6. ParallelWrite the follow-upsWrite from {{verified}} only, keeping item IDs in brackets (e.g. '[A2]') and dates as given. Add no tasks, decisions or dates. Short plain sentences, no pleasantries.
    • Recap emailFrom {{sender}} to all attendees. Subject: 'Recap: <goal in under 8 words> – <meeting date>'. Sections: Outcome (one line on the goal), Decisions, Action items (owner – task – due date), Open questions (and who will answer), Needs attention. Under 300 words.
    • Per-owner messagesOne chat message per owner, under 80 words: their tasks with due dates and done criteria, plus open questions assigned to them. If any action or question has no owner, add a message to {{sender}} listing them and asking them to assign each.
    • Ticket listOne ticket per action item for {{tracker}}: Title (verb first, under 70 characters), Description (two sentences of context, done criteria, the quote), Assignee, Due date (ISO or blank), Labels ('confirm' for soft commitments). A markdown table, then the same rows as CSV with a header.
  7. Review loopTighten the drafts1. Every action item line has a bracketed ID and an owner name or 'Unassigned'. 2. Every due date starts with YYYY-MM-DD or 'no date'; the original phrase may follow in brackets. 3. Recap email under 300 words; each per-owner message under 80. 4. No filler openers or closers ('Hope you're well', 'Let me know if you have any questions!', 'Great meeting today'). 5. The ticket CSV has as many data rows as the ticket table. 6. Nothing under Open questions is described anywhere as decided.
  8. ApprovalApprove before sendingReview {{followups}} and the 'Needs attention' and 'Removed' lists in {{verified}}. Assign unowned items, then approve, edit or reject. Nothing is sent.→ chat
  9. OutputReturn the follow-upsReturn {{followups}} and {{verified}}.→ chat

Good for

Anyone who runs meetings and wants decisions, owners and dates written down before they are forgotten.

Last reviewed

Install as a skill

The whole workflow as one SKILL.md. Install it in Claude Code, Codex or Copilot and ask your agent to run “Meeting transcript to decisions and follow-ups”.

Get the meeting-transcript-to-follow-ups skill

What each step does

  1. 1. Paste the transcript (Trigger)

    Paste {{transcript}} (or rough notes) with {{attendees}} and roles, the {{meeting_goal}} and {{meeting_date}}. {{sender}} sends the recap; {{tracker}} sets the ticket format. Nothing is sent or created.

  2. 2. Map speakers to attendees (Prompt)

    From {{transcript}} and {{attendees}}, make a table: speaker label as written | attendee | role. Match on names, initials and self-introductions; if unsure, write 'Unknown' and quote the ambiguous line. Then list attendees who never spoke and people mentioned who aren't attendees (they can own tasks, flagged external). If there are no speaker labels at all, say so first; every owner is then unconfirmed.

  3. 3. Extract in parallel (Parallel)

    Work only from {{transcript}}, using {{speakers}} for who said what. Every item needs a verbatim quote (up to 30 words) with speaker and timestamp if any. Never infer an item nobody said. If none, write 'None found.' Number items with your part's prefix.

    • Decisions: Decisions (D1, D2…): the decision in one sentence, who made or confirmed it, the quote. It needs agreement or a clear call from someone with authority. Ideas, preferences and 'let's think about it' go under 'Not decided' at the end, with quotes.
    • Action items: Every commitment or assignment (A1, A2…): task as a verb phrase, owner exactly as said ('I', 'you', 'Tom', 'marketing'), due date exactly as said ('by Friday', or 'none'), done criteria from the transcript (or 'not stated'), the quote. Include soft commitments ('I can take a look'), marked soft.
    • Open questions: Unanswered questions and deferred topics ('let's park this') as Q1, Q2…: the question, who raised it, who was named to answer it if anyone, the quote.
    • Risks and blockers: Risks, dependencies, blockers and concerns raised (R1, R2…): the risk, who raised it, what it affects if obvious, the quote. Add none of your own.
  4. 4. Resolve owners and dates (Prompt)

    Using {{extracted}}, {{speakers}} and {{attendees}}, for a meeting on {{meeting_date}}: 1. Replace each owner reference with a full name: 'I' = the quote's speaker; 'you' = the person addressed (named in the same or previous sentence, or the previous speaker). Teams stay teams, flagged 'needs a named owner'. Note what each was resolved from. 2. Convert relative dates from {{meeting_date}} to 'YYYY-MM-DD (original phrase)': 'Friday' = the first Friday after; 'end of month' = its last day. 'Next sprint', 'soon', 'ASAP' become 'no date (original phrase)', flagged. 3. Merge duplicates, keeping the clearer quote. 4. End with 'Needs attention': actions with no owner, no date or a non-attendee owner; soft commitments; unassigned open questions; unresolved owners. One markdown table per section, IDs kept.

  5. 5. Check every item against the transcript (Prompt)

    Check each item in {{items}} against {{transcript}}: is the quote there word for word (allowing for filler words and punctuation), and does it support the item, including owner, date and wording? Mark each Verified, Corrected (fixed to what was said, noting the change) or Removed (quote missing or unsupportive). Say in one line whether the meeting reached {{meeting_goal}} (reached, partly, not), citing decision IDs. Return tables of Verified and Corrected items (with owners, dates, done criteria), then 'Needs attention', then 'Removed' with reasons.

  6. 6. Write the follow-ups (Parallel)

    Write from {{verified}} only, keeping item IDs in brackets (e.g. '[A2]') and dates as given. Add no tasks, decisions or dates. Short plain sentences, no pleasantries.

    • Recap email: From {{sender}} to all attendees. Subject: 'Recap: <goal in under 8 words> – <meeting date>'. Sections: Outcome (one line on the goal), Decisions, Action items (owner – task – due date), Open questions (and who will answer), Needs attention. Under 300 words.
    • Per-owner messages: One chat message per owner, under 80 words: their tasks with due dates and done criteria, plus open questions assigned to them. If any action or question has no owner, add a message to {{sender}} listing them and asking them to assign each.
    • Ticket list: One ticket per action item for {{tracker}}: Title (verb first, under 70 characters), Description (two sentences of context, done criteria, the quote), Assignee, Due date (ISO or blank), Labels ('confirm' for soft commitments). A markdown table, then the same rows as CSV with a header.
  7. 7. Tighten the drafts (Review loop)

    1. Every action item line has a bracketed ID and an owner name or 'Unassigned'. 2. Every due date starts with YYYY-MM-DD or 'no date'; the original phrase may follow in brackets. 3. Recap email under 300 words; each per-owner message under 80. 4. No filler openers or closers ('Hope you're well', 'Let me know if you have any questions!', 'Great meeting today'). 5. The ticket CSV has as many data rows as the ticket table. 6. Nothing under Open questions is described anywhere as decided.

  8. 8. Approve before sending (Approval)

    Review {{followups}} and the 'Needs attention' and 'Removed' lists in {{verified}}. Assign unowned items, then approve, edit or reject. Nothing is sent.

  9. 9. Return the follow-ups (Output)

    Return {{followups}} and {{verified}}.

Use it in your own agent

Fill in the inputs
Too long for an Open in link: copy the chat prompt below instead.6 inputs use their example until you fill them in.

Paste into ChatGPT, Claude or Gemini. Parallel steps run one after another, and approvals become “wait for my OK”.

meeting-transcript-to-follow-ups.txt
You're going to run a multi-step workflow: Meeting transcript to decisions and follow-ups.

Inputs:
- transcript: [00:02] Priya: Goal today is the billing page launch date. [00:41] Tom: Migration needs two sprints, so earliest is Jan 12. [01:10] Priya: OK, Jan 12 it is. Tom, can you send the cutover plan by Friday? [01:15] Tom: Yes. [01:30] Lena: Who writes the announcement? [01:34] Priya: Let's park that.
- attendees: Priya Shah (Head of Product, chair), Tom Becker (Engineering lead), Lena Ortiz (Marketing), Sam Wu (contract designer)
- meeting_goal: Decide the launch date for the new billing page and who owns the data migration
- meeting_date: 2026-11-16 (Monday)
- sender: Priya Shah
- tracker: Linear

Work through these steps in order. Label each step's output with its number. Where a step says to wait for my OK, stop and wait.

1. **Map speakers to attendees** — From [00:02] Priya: Goal today is the billing page launch date. [00:41] Tom: Migration needs two sprints, so earliest is Jan 12. [01:10] Priya: OK, Jan 12 it is. Tom, can you send the cutover plan by Friday? [01:15] Tom: Yes. [01:30] Lena: Who writes the announcement? [01:34] Priya: Let's park that. and Priya Shah (Head of Product, chair), Tom Becker (Engineering lead), Lena Ortiz (Marketing), Sam Wu (contract designer), make a table: speaker label as written | attendee | role. Match on names, initials and self-introductions; if unsure, write 'Unknown' and quote the ambiguous line. Then list attendees who never spoke and people mentioned who aren't attendees (they can own tasks, flagged external). If there are no speaker labels at all, say so first; every owner is then unconfirmed. Save the result as `speakers`.
2. **Extract in parallel** — Do each of these separately, then combine them. Work only from [00:02] Priya: Goal today is the billing page launch date. [00:41] Tom: Migration needs two sprints, so earliest is Jan 12. [01:10] Priya: OK, Jan 12 it is. Tom, can you send the cutover plan by Friday? [01:15] Tom: Yes. [01:30] Lena: Who writes the announcement? [01:34] Priya: Let's park that., using {{speakers}} for who said what. Every item needs a verbatim quote (up to 30 words) with speaker and timestamp if any. Never infer an item nobody said. If none, write 'None found.' Number items with your part's prefix. Save the result as `extracted`.
   - **Decisions**: Decisions (D1, D2…): the decision in one sentence, who made or confirmed it, the quote. It needs agreement or a clear call from someone with authority. Ideas, preferences and 'let's think about it' go under 'Not decided' at the end, with quotes.
   - **Action items**: Every commitment or assignment (A1, A2…): task as a verb phrase, owner exactly as said ('I', 'you', 'Tom', 'marketing'), due date exactly as said ('by Friday', or 'none'), done criteria from the transcript (or 'not stated'), the quote. Include soft commitments ('I can take a look'), marked soft.
   - **Open questions**: Unanswered questions and deferred topics ('let's park this') as Q1, Q2…: the question, who raised it, who was named to answer it if anyone, the quote.
   - **Risks and blockers**: Risks, dependencies, blockers and concerns raised (R1, R2…): the risk, who raised it, what it affects if obvious, the quote. Add none of your own.
3. **Resolve owners and dates** — Using {{extracted}}, {{speakers}} and Priya Shah (Head of Product, chair), Tom Becker (Engineering lead), Lena Ortiz (Marketing), Sam Wu (contract designer), for a meeting on 2026-11-16 (Monday):
1. Replace each owner reference with a full name: 'I' = the quote's speaker; 'you' = the person addressed (named in the same or previous sentence, or the previous speaker). Teams stay teams, flagged 'needs a named owner'. Note what each was resolved from.
2. Convert relative dates from 2026-11-16 (Monday) to 'YYYY-MM-DD (original phrase)': 'Friday' = the first Friday after; 'end of month' = its last day. 'Next sprint', 'soon', 'ASAP' become 'no date (original phrase)', flagged.
3. Merge duplicates, keeping the clearer quote.
4. End with 'Needs attention': actions with no owner, no date or a non-attendee owner; soft commitments; unassigned open questions; unresolved owners.
One markdown table per section, IDs kept. Save the result as `items`.
4. **Check every item against the transcript** — Check each item in {{items}} against [00:02] Priya: Goal today is the billing page launch date. [00:41] Tom: Migration needs two sprints, so earliest is Jan 12. [01:10] Priya: OK, Jan 12 it is. Tom, can you send the cutover plan by Friday? [01:15] Tom: Yes. [01:30] Lena: Who writes the announcement? [01:34] Priya: Let's park that.: is the quote there word for word (allowing for filler words and punctuation), and does it support the item, including owner, date and wording? Mark each Verified, Corrected (fixed to what was said, noting the change) or Removed (quote missing or unsupportive).
Say in one line whether the meeting reached Decide the launch date for the new billing page and who owns the data migration (reached, partly, not), citing decision IDs.
Return tables of Verified and Corrected items (with owners, dates, done criteria), then 'Needs attention', then 'Removed' with reasons. Save the result as `verified`.
5. **Write the follow-ups** — Do each of these separately, then combine them. Write from {{verified}} only, keeping item IDs in brackets (e.g. '[A2]') and dates as given. Add no tasks, decisions or dates. Short plain sentences, no pleasantries. Save the result as `followups`.
   - **Recap email**: From Priya Shah to all attendees. Subject: 'Recap: <goal in under 8 words> – <meeting date>'. Sections: Outcome (one line on the goal), Decisions, Action items (owner – task – due date), Open questions (and who will answer), Needs attention. Under 300 words.
   - **Per-owner messages**: One chat message per owner, under 80 words: their tasks with due dates and done criteria, plus open questions assigned to them. If any action or question has no owner, add a message to Priya Shah listing them and asking them to assign each.
   - **Ticket list**: One ticket per action item for Linear: Title (verb first, under 70 characters), Description (two sentences of context, done criteria, the quote), Assignee, Due date (ISO or blank), Labels ('confirm' for soft commitments). A markdown table, then the same rows as CSV with a header.
6. **Tighten the drafts** — Review loop (max 2 passes): 1. Every action item line has a bracketed ID and an owner name or 'Unassigned'.
2. Every due date starts with YYYY-MM-DD or 'no date'; the original phrase may follow in brackets.
3. Recap email under 300 words; each per-owner message under 80.
4. No filler openers or closers ('Hope you're well', 'Let me know if you have any questions!', 'Great meeting today').
5. The ticket CSV has as many data rows as the ticket table.
6. Nothing under Open questions is described anywhere as decided. Save the result as `followups`.
7. **Approve before sending** — Show me the result and wait for my OK before the next step: Review {{followups}} and the 'Needs attention' and 'Removed' lists in {{verified}}. Assign unowned items, then approve, edit or reject. Nothing is sent.
8. **Return the follow-ups** — Finish: Return {{followups}} and {{verified}}.

Want different steps? Open it in the workflow builder.