Meeting Minutes and Management Briefs

Problem

In consulting projects, meeting transcripts, cross-session notes, and monthly briefs often get mixed together. Facts may lack sources, action items may lack owners and deadlines, client names and amounts may leak into documents, and outbound briefs still need checks for letter numbers, addressees, and previous commitments. This skill turns “meeting minutes” and “monthly briefs” into executable workflows with traceable facts, deliverable documents, and anonymized client data.

How It Works

• Four-level routing: It classifies input into Quick, Mini, Full, or Brief modes so lightweight tasks do not trigger heavy pipelines.
• Minutes workflow: It reads the transcript and client code, identifies the work type, and writes an evidence matrix before prose. Fact sentences must be marked as 【实证】, 【估算】, or 【常识】; 【实证】 items require a source location.
• Action-item constraints: Items must include content, owner, tracker, deadline, and deliverable; vague deadlines such as soon or ASAP are disallowed.
• Brief mode: It aggregates multiple slices, scans calendar sources and deliverables, and generates structured sections for current work, completion status, and next-month plans. Human review is required before generating the docx.
• Client memory: It maintains client-code directories and README files, tracking undelivered commitments, recurring issues, and recent meetings for cross-session recall.

Boundaries

It accepts .docx, .txt, and .md transcripts, but does not transcribe audio or video. Deep-interview cases are deferred to an interview-insight skill. Outbound briefs must be reviewed, and client names, amounts, and organizational details are anonymized using codes and ranges.