Meeting Minutes and Action-Item Closure
A meeting isn’t the finish line — turning the discussion into actionable to-dos is. This case shows how to use LanMate to extract key information from meeting records, generate structured minutes and an action-item list, and notify the right people via Lansenger.
Skills Used
- Built-in skills (installed with LanMate, ready out of the box): Lansenger integration (lanmate-lansenger), Word documents (lanmate-docx), Excel spreadsheets (lanmate-xlsx)
- Skill Store: Meeting Minutes Generator — extract topics, decisions, and to-dos into structured minutes; Meeting Notes Extractor — turn colloquial transcripts into key points; Plans to Tasks — break to-dos into an actionable task list
Pain Points
- Meeting discussions are spoken and informal; decisions, disagreements, and action items are all mixed together, making manual organization time-consuming
- After writing the minutes, you still have to notify each participant one by one, switching between multiple apps
- Action items lack owners and deadlines, so no one follows up after the meeting
Recommended Workflow
| Step |
What LanMate Does |
What You Need to Confirm |
| 1 |
Pull meeting discussion records from a Lansenger group chat, or read a meeting transcript you uploaded |
Whether the records fully cover the meeting content |
| 2 |
Automatically extract agenda items, decisions, and action items, and generate structured minutes |
Whether names and dates are accurate |
| 3 |
Output a Word minutes document and an Excel action-item list |
Whether the format is ready for distribution |
| 4 |
Send a minutes summary to the meeting group via Lansenger to notify the relevant people |
Whether the group name and content are correct |
Prompt Examples
Generate Minutes from Lansenger Group Chat
Pull the chat history from the "Project Review Group" for the last day, and extract the agenda items, decisions, and action items from the meeting discussion.
Generate a structured set of meeting minutes that includes:
- Meeting time and participants
- Discussion topics and key points
- List of decisions
- Action items table (task, owner, deadline)
For owners or dates that cannot be confirmed from the records, write "TBC" — do not fill them in yourself.
Output a Word document and an Excel action-item list.
Generate Minutes from an Uploaded Transcript
Please read the meeting transcript I uploaded and organize it into structured meeting minutes.
It must include: meeting conclusions, action items, owners, deadlines, and items to be confirmed.
For owners or dates that cannot be confirmed from the original text, write "TBC" — do not fill them in yourself.
Output Word minutes and an Excel action-item list.
Revision: Supplement Action-Item Details
Please modify the previous version of the minutes — do not regenerate the entire document.
Modification requirements:
- For action items with "TBC" owners, fill in based on the discussion: Zhang San is responsible for API coordination, Li Si is responsible for the test plan
- Add deadlines: API coordination by August 15, test plan by August 20
- Add a "Next meeting time" section at the end of the minutes: August 22 at 2:00 PM
Output the revised v2 Word document.
Send Minutes to a Lansenger Group
Organize a summary of the meeting minutes (topics + decisions + action items) into a concise Markdown text,
and send it to the "Project Review Group."
Keep the summary under 500 words, highlighting decisions and action items.
Acceptance Criteria
- Every decision can be traced back to the original chat record or transcript
- Action items do not miss owners or deadlines; anything that can’t be confirmed is marked “TBC”
- The Word minutes are properly formatted and ready for distribution
- The Excel action-item list includes three columns: task, owner, and deadline
- The Lansenger group notification is concise and highlights decisions and action items
Common Mistakes
| Common Mistake |
Why It Happens |
Better Practice |
| Generating minutes from an incomplete transcript |
Recording interruptions or transcription omissions |
Check record completeness first; note any missing parts |
| Letting the AI fill in names and dates on its own |
The model tends to give complete answers |
State explicitly in the prompt: “write TBC for anything you can’t confirm” |
| Sending to the group without confirmation |
Rushing to finish the process |
Preview in the conversation first, then send after confirming |
| Minutes too long; the group notification misses the point |
Copying the full text |
Send only a summary to the group; send the full minutes as a file |