Government Meeting Minutes Drafter

Problem

Internal government, public-institution, and state-owned-enterprise meeting notes often arrive as loose transcripts, pasted text, or mixed formats. The hard part is not summarizing, but converting those notes into formal minutes without first-person tone, casual phrasing, unresolved disagreements, or missing ownership and deadlines.

How it works

This skill starts from docx, md, pdf, txt, or pasted text. It checks the input, extracts text, infers the meeting type, and splits the record into agenda items. It then drafts the body using a fixed sequence: procedure, opinions, decisions, and actions. In formal mode, it prefers standardized phrases such as meeting heard, meeting deliberated, meeting decided, and meeting required, rather than casual expressions like the leader required or everyone agreed.

It also handles the parts that are easy to lose in a meeting: open items, disagreements, and source attribution. Open items are marked for follow-up; conflicting positions can be flagged with 【待选择】 and listed at the end; opinion sources can be retained as end-of-paragraph annotations. When available, it can integrate with gov-doc-format to produce a formatted docx draft; otherwise it falls back to Markdown. It also emits a separate action-item tracker that lists owners, supporting departments, deadlines, and pending items.

Boundaries

This is best for formal meeting materials in party-government organs, public institutions, or state-owned enterprises, especially when there is already a text transcript. It does not transcribe audio directly, and legacy .doc files may need to be saved as .docx. For informal internal notes, it can relax the style, but still needs clear owners, deadlines, and unresolved points.