Meeting to Actions

Meeting transcripts and messy notes often rot in folders because nobody wants to parse them for tasks. This skill extracts clear decisions, owners, and deadlines so you can update your project management tools without rereading the entire transcript.

What it does

• Extract decisions by separating confirmed outcomes from items still under discussion.
• Assign ownership by mapping specific tasks to individuals mentioned in the source.
• Identify blockers to highlight dependencies that prevent progress on action items.
• Draft follow-ups to create ready-to-send messages for Slack or email.
• Surface gaps by listing tasks that lack clear owners or defined due dates.

How it works

1. Provide source material by pasting a Zoom transcript, raw meeting notes, or an email chain.
2. Review the action record which categorizes points into decisions, tasks, and blockers.
3. Refine the output if you need specific follow-up drafts or ticket descriptions based on the extracted data.

Frameworks & tools

Works with any text-based input including Zoom, Google Meet, Microsoft Teams transcripts, Slack threads, and Markdown notes.

Why this beats prompting it yourself

Generic prompts often miss the nuance between a "discussed idea" and a "final decision." This skill enforces strict guardrails to separate confirmed actions from open questions, ensuring you don't assign tasks based on brainstormed hypotheticals.

Use cases

• Post-meeting cleanup for weekly syncs to keep the team focused.
• Transcript synthesis to turn 60-minute recordings into five-minute reads.
• Ticket preparation by converting discussion threads into structured Jira or Linear tasks.
• Stakeholder reporting to provide quick executive summaries of project status.

Known limitations

Does not automatically send emails or update external APIs. Accuracy depends on the clarity of names and dates mentioned in the source text.