编程

Board Minutes

试用

Write formal board meeting minutes from an agenda, notes, transcript, or discussion summary. Use when asked to draft board minutes, governance minutes, meeti...

它能做什么

Produce formal board meeting minutes that are concise, defensible, and useful as the official record. The minutes should capture what the board considered, what was decided, what actions were assigned, and any formal resolutions — without turning the document into a transcript.

技能文档

Board Minutes Skill

Produce formal board meeting minutes that are concise, defensible, and useful as the official record. The minutes should capture what the board considered, what was decided, what actions were assigned, and any formal resolutions — without turning the document into a transcript.

What This Skill Produces

  • Formal board minutes ready for review by the chair, company secretary, or governance lead
  • A clear record of attendees, apologies, quorum, conflicts of interest, agenda items, decisions, resolutions, and actions
  • An action register with owners, due dates, and status
  • Optional draft approval wording for the next board meeting

Required Inputs

Ask for these if not already provided:

  • Organisation / company name and board or committee name
  • Meeting date, time, location, and meeting type (regular / special / committee)
  • Attendees, apologies, guests, and chair / secretary names
  • Agenda or topic list
  • Meeting notes, transcript, or bullet summary of the discussion
  • Decisions made, formal resolutions passed, votes, abstentions, or objections
  • Actions agreed — owner and due date for each, if known
  • Any conflicts of interest, confidential items, or matters to redact from circulation

Minute-Taking Principles

  • Record decisions, rationale, and actions — not a verbatim transcript.
  • Use neutral, factual language. Avoid attributing opinions unless attribution is necessary for a conflict, dissent, or formal record.
  • Separate discussion from decisions. A reader should be able to find what was approved and who must do what next.
  • Preserve exact resolution wording when the source materials provide it; formal resolutions often need verbatim treatment.
  • Keep legal precision without over-lawyering. If the notes mention regulated, legal, employment, or financial matters, flag that the draft should be reviewed by the appropriate governance or legal owner.
  • Do not invent quorum, votes, attendees, or resolutions. Mark unknown items as [to confirm].

Process

  1. Identify meeting metadata — organisation, board, date, location, chair, secretary, attendees, apologies, guests, and quorum status.
  2. Group notes by agenda item — preserve the board's agenda order where possible.
  3. Extract formal decisions — approvals, rejections, deferrals, delegated authority, and resolutions.
  4. Extract action items — owner, due date, dependency, and follow-up forum.
  5. Flag governance-sensitive items — conflicts of interest, dissent, recusal, privileged discussion, confidential information, and items requiring legal/secretarial review.
  6. Draft minutes in official-record style — concise past tense, neutral tone, no transcript filler.
  7. Add an action register and approval footer — make follow-up and next-meeting approval straightforward.

Output Format


Minutes of the [Board / Committee] Meeting

Organisation: [Organisation name] Meeting: [Board / Committee name] Date and time: [Date, start–end time] Location: [Location / video conference] Chair: [Name] Minute taker / secretary: [Name]

1. Attendance

Present: [Names and roles] Apologies: [Names] In attendance / guests: [Names, roles, agenda items attended for] Quorum: [Confirmed / Not confirmed / To confirm]

2. Conflicts of Interest

[State whether any conflicts were declared. If a conflict was declared, record the person, agenda item, and whether they recused themselves. If unknown, write [to confirm].]

3. Approval of Previous Minutes

[Record whether previous minutes were approved, amended, or deferred. Include action follow-up if relevant.]

4. Agenda Items

Repeat this structure for each agenda item.

4.[N] [Agenda Item]

Paper / presenter: [Paper reference or presenter, if known]

Discussion summary: [Concise factual summary of the material points considered by the board. Capture key risks, options, and rationale. Do not write a transcript.]

Decision / resolution:

  • [Approved / Not approved / Deferred / Noted]
  • Formal resolution wording, if applicable: "Resolved that [exact decision]."

Actions:

ActionOwnerDue dateNotes
[Action][Owner][Date / TBC][Context]

5. Any Other Business

[Items raised outside the agenda, with any decisions or actions. If none: "No further business was raised."]

6. Next Meeting

Date: [Date / TBC] Location: [Location / TBC] Key agenda items to carry forward: [List]

Action Register

#ActionOwnerDue dateStatus
1[Action][Owner][Date]Open

Approval

These minutes were approved by the board on [date] as an accurate record of the meeting held on [meeting date].

Chair: ______________________ Date: ______________________


Governance Review Notes

  • Items marked [to confirm]: [List]
  • Potentially sensitive items for review: [Legal / financial / employment / confidentiality / conflict-of-interest items]
  • Open drafting questions: [Anything the minute taker must verify before circulation]

Quality Checks

  • The minutes are concise and not a transcript
  • Every formal decision or resolution is clearly separated from discussion
  • Every action has an owner and due date, or is marked [to confirm]
  • Attendance, apologies, guests, chair, secretary, and quorum are recorded or marked [to confirm]
  • Conflicts of interest and recusals are captured if present
  • Sensitive or uncertain items are flagged for governance/legal review rather than guessed
  • The final draft can be approved as an official record without relying on hidden context

Anti-Patterns

  • Do not invent resolutions, votes, attendees, quorum, or action owners when the notes are silent
  • Do not write a blow-by-blow transcript; minutes capture material discussion, decisions, and actions
  • Do not use emotive or blame-heavy language; keep the official record neutral and factual
  • Do not bury decisions inside long paragraphs; make approvals, deferrals, and actions easy to find
  • Do not omit conflicts of interest, dissent, abstentions, or recusals when they appear in the source notes
  • Do not provide legal advice; flag governance-sensitive items for qualified review

相关技能

把自然语言描述转为结构化 JSON,并由 mcp-diagram-generator MCP 服务生成 Draw.io、Mermaid 或 Excalidraw 图表文件。

作者 nssa.io1.0k 次安装47 星标

以 AI 机器人身份加入视频会议,提供语音、虚拟形象与屏幕共享四种模式。

作者 johnpatternai22 次安装8 星标

在本地磁盘以分类纯 Markdown 文件保存需要长期留存的事实,与智能体内置记忆并存。

作者 Iván559 次安装18 星标

诊断生产力系统反复失效的根因,给出最小干预——容量测算、瓶颈定位、可靠的本地记录。

作者 Iván855 次安装69 星标

从 AdMapix API 拉取广告创意、应用、榜单和收入预估等数据,原样返回结构化 JSON。

作者 fly0pants4.3k 次安装296 星标

mohitagw15856 的更多技能

浏览全部技能

Extract a brand's visual and verbal identity into an applicable guideline kit — tokens, voice rules, and do/don't pairs — then apply it consistently to any a...

作者 mohitagw158562 次安装

Write an AI usage policy people can actually follow — approved tools, data rules, disclosure duties, and review obligations, in one page instead of legal fog...

作者 mohitagw15856

Write an executive summary for any document, report, or proposal. Use when asked to write an executive summary, management summary, briefing paper, or one-pa...

作者 mohitagw158562 次安装

Convert a git log, commit list, or release notes into a polished, user-facing changelog. Use when writing release notes, generating a CHANGELOG.md entry, or...

作者 mohitagw158562 次安装

Document or design a database schema with entity relationships, table definitions, constraints, indexes, and access patterns. Use when asked to design a data...

作者 mohitagw158561 次安装

Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colle...

作者 mohitagw158561 次安装