Meeting Minutes Generator

Problem Addressed

Meeting notes often remain scattered across chat logs, whiteboards, transcripts, and ad hoc notes. After a meeting, the hard part is separating who owns what, what has been decided, and what still needs follow-up from the noise. This skill targets that office workflow: when a user provides discussion content and asks for meeting minutes, it turns loose information into a structured record instead of merely paraphrasing the source.

How It Works

The main steps are:

• Extract key elements: identify topics, decisions, action items, and owners.
• Organize by template: output a common company meeting structure in Markdown / Word format.

The default template includes:

• Meeting topic
• Time and attendees
• Discussion summary
• Decisions
• Action items

This makes the output easier to archive, sync into documentation systems, or convert into tasks. Engineers can treat it as an intermediate artifact for writing collaboration docs, generating task cards, or drafting weekly reports.

Boundaries

It fits best when there is already a clear discussion text to summarize. It does not handle audio transcription, attendee identification, or permission management. If the input lacks owners, deadlines, or decision context, output quality will drop. Before formal archiving, review Action items ownership and priority manually.