Meeting Decision Log Skill

The problem

Meeting notes are often walls of text where critical commitments and technical blockers get buried. Project momentum stalls when "we discussed" never turns into "who is doing what by when."

What it does

• Extracts concrete decisions, actions, and open questions from messy transcripts or chat logs.
• Maps every task to an owner and deadline, explicitly flagging items that are unassigned or lack a date.
• Identifies technical, approval, and external dependencies to surface potential project bottlenecks.
• Detects decision conflicts and accountability gaps where tasks lack clear deliverables or owners.
• Generates structured decision logs and executive snapshots for immediate team distribution.

Why this beats prompting it yourself

General LLMs often hallucinate owners or turn vague suggestions into firm commitments. This skill uses a strict verification workflow to distinguish confirmed decisions from mere discussion, preserving original relative deadlines and identifying specific gaps in accountability that manual prompting usually misses.

Use cases

• Converting a raw Zoom or Teams transcript into a structured technical decision log.
• Performing an accountability audit on meeting notes to find tasks missing owners or dates.
• Generating a "next meeting" agenda based on unresolved questions and blocked actions.
• Mapping complex dependencies between cross-functional teams after a project kickoff.

Known limitations

Requires a source text like a transcript, notes, or agenda. It cannot attend live meetings or access external calendar data directly.