summarize-meeting

This skill acts as an intelligent assistant for product managers and team leads tasked with maintaining clarity and accountability following team discussions. It automates the tedious process of synthesizing raw meeting transcripts or recordings into professional, accessible documentation. By processing unstructured meeting input, the skill identifies the core narrative, captures high-stakes decisions, tracks individual accountability via action items, and surfaces lingering blockers or open questions. It is designed to bridge the gap between spoken conversation and actionable documentation, ensuring that project momentum is preserved regardless of who was able to attend the sync.

• Automatically extracts meeting metadata including participants, roles, dates, and core discussion topics.

• Generates structured summaries using a standardized markdown template that emphasizes readability and accessibility for all stakeholders.

• Identifies and tables action items with explicit owner names and due dates to improve follow-through and project execution.

• Categorizes decisions and unresolved open questions to provide clear visibility into team progress and potential risks.

• Applies a 'simple language' filter, ensuring that technical jargon is either simplified or briefly explained for non-technical team members.

• Adopts an inclusive 'we' voice to foster a collaborative culture within product teams.

• For best results, provide a clear meeting transcript, video recording link, or raw meeting notes; the skill can also leverage web search to fetch project background or context if required.

• Output is generated as a standard markdown file formatted as Meeting-Summary-[date]-[topic].md, ready for direct inclusion into project repositories or team knowledge bases like Notion, Confluence, or GitHub wikis.

• The skill maintains strict objectivity, focusing on capturing the facts of the discussion rather than subjective interpretations.

• It is highly effective for post-meeting recaps, writing minutes for stakeholder syncs, processing design critiques, or documenting sprint retrospectives.

• While optimized for product management workflows, it is universally applicable for any professional scenario requiring documented accountability and clarity.