Meeting Actions

The problem

Meeting notes often end up as wall-of-text transcripts where commitments and choices are buried. Developers and managers waste time manually digging through these logs to figure out who owns which task and what was actually agreed upon.

What it does

• Extracts specific decisions and action items from a single meeting transcript or note file.
• Requires explicit citations for every claim, linking decisions back to specific quotes or timestamps.
• Identifies gaps in documentation, such as missing owners, unresolved questions, or vague deadlines.
• Differentiates between actual decisions and mere brainstormed proposals to prevent false commitments.
• Drafts tracker updates without mutating your existing data until you explicitly approve the changes.

Why this beats prompting it yourself

Generic prompts often hallucinate owners or invent "logical" deadlines to be helpful. This skill enforces strict evidence-based extraction, ensuring that if a name or date wasn't explicitly mentioned, it remains marked as unresolved rather than guessed.

Use cases

• Converting a messy Zoom or Teams transcript into a clean, cited action plan.
• Auditing project meetings to ensure every decision has a recorded owner and ISO-formatted date.
• Generating a gap report for project managers to show exactly what information was missing from a call.
• Preparing draft ticket updates for a CRM or task tracker based on call outcomes.

Known limitations

Does not support multi-meeting files, audio transcription, or automated calendar syncing. Requires a manually provided ISO date and timezone to resolve relative time references.