Yggdrasil
MCP ServersMCP 伺服器 SKILLs技能 PlugIns解決方案 Asgard AI SolutionAsgard AI 方案 Submit Listing申請上架 GitHub
M

Meeting Minutes 會議紀錄

Released已發布
methodology ops

Create structured meeting minutes with decisions, action items, and follow-up tracking. Use this skill when the user needs to document meetings effectively, track action items, improve meeting productivity, or set up a meeting note system — even if they say 'take notes for this meeting', 'what was decided', 'who's responsible for what', or 'our meetings have no follow-through'.

營運方法論技能:Meeting Minutes 分析與應用。

View on GitHub在 GitHub 查看

Methodology 方法論

IRON LAW: Every Meeting Must Produce Decisions + Action Items

If a meeting ends with no documented decisions and no action items with
owners and deadlines, the meeting was a waste of time. Capture these
DURING the meeting, not after. Minutes without action items are a diary.

Meeting Minutes Template

# Meeting: {Title}
Date: {YYYY-MM-DD} | Time: {HH:MM-HH:MM} | Location: {room/link}
Attendees: {names}
Absent: {names}
Facilitator: {name} | Note-taker: {name}

Output Format輸出格式

# Meeting Minutes: {Title} — {Date}

Gotchas注意事項

  • Minutes ≠ transcript: Don't capture everything said. Capture: decisions, action items, key disagreements, and context needed to understand decisions later.
  • Action items without deadlines don't get done: "ASAP" is not a deadline. Every action item needs a specific date.
  • The note-taker has power: They decide what's recorded as a "decision." Assign this role intentionally.
  • Follow up on action items: Minutes sent without follow-up are ignored. Review action item status at the START of the next meeting.
  • Recurring meetings need structure: Weekly standups, monthly reviews, and quarterly planning each need different minute formats. One size doesn't fit all.

References參考資料

  • For meeting facilitation techniques, see references/facilitation.md

Tags標籤

businessmeetingsdocumentationproductivity