Smart Meeting Minutes

Problem

Raw meeting material often arrives as verbose transcripts, scattered notes, or verbal follow-ups. If shared directly, key decisions get buried in discussion, action items may lack owners and deadlines, and later accountability becomes hard to verify. This skill turns that input into an archiveable, syncable, followable meeting minutes document rather than a stream-of-consciousness log.

Workflow and limits

It extracts meeting metadata, agenda items, resolutions, action items, open questions, and next meeting plans, then structures them using a standard template:
- Meeting basics: topic, time, location, chair, attendees.
- Core content and decisions: by agenda item, using the pattern 'discussion core + final decision,' keeping conclusions and special notes.
- Action items: table with item, task, owner, collaborators, deadline, deliverable, and notes; vague terms like 'as soon as possible' are avoided.
- Open issues: unresolved items, follow-up method, and expected feedback time.

Output is Markdown by default; for Word delivery, python-docx can be used to create a .docx file named 【会议纪要】YYYY年MM月DD日-XX会议. Structured JSON can be batch-rendered through generate_minutes.py. Before final output, missing owners or deadlines should be confirmed, debate details should be excluded, and no confirmed decision or action item should be omitted.