meeting action follow up builder

The problem

Meeting notes and transcripts usually sit in documents where action items lose their owners, deadlines are guessed, and critical decisions lack rationale. Developers and PMs waste time manually parsing messy text into trackers only to realize half the commitments are missing clear accountability.

What it does

• Extracts decisions, commitments, owners, and deadlines from raw transcripts or notes.
• Normalizes every action item with unique IDs, explicit owners, and observable acceptance criteria.
• Maps dependencies and risks to ensure blockers are identified before they stop progress.
• Generates a comprehensive validation report to flag missing owners or unstated deadlines.
• Produces ready-to-use follow-up artifacts including action tables, risk registers, and next-meeting pre-reads.

Why this beats prompting it yourself

Standard LLM prompts often hallucinate deadlines or assign tasks to "the team" when owners aren't specified. This skill enforces a strict verification protocol that distinguishes actual decisions from mere suggestions and requires every output to be traceable back to specific source text.

Use cases

• Convert a messy Zoom transcript into a structured Jira-ready action item table.
• Audit a recorded project kickoff to ensure every risk and dependency was captured.
• Create a "next-meeting context" document that carries forward unresolved questions and blocked items.
• Generate a formal decisions log with rationale and dissent for compliance and traceability.

Known limitations

Does not perform live facilitation or transcription. Requires existing text-based artifacts like notes, chat logs, or transcripts to function.