Board & Governance

Board and Governance defines a small record structure for meetings, resolutions, action items, and risks. Its recommendation keeps meetings, papers, and decisions separate but joined by the meeting, with action owners and due dates. The workflow schedules a meeting, circulates papers, holds the meeting, records minutes, and tracks actions. The design focuses on preventing lost follow-up actions rather than simply collecting minutes.

The skill distinguishes advice, review, build, and conversion requests. It gives a short recommendation by default and generates artifacts when requested. Missing questions concern the board or investor body, membership and committees, cadence, advance papers, formal minutes, recorded decisions, action assignment, existing storage, and whether meeting records, an action log, or both are needed. It asks one useful question at a time, skips confirmed facts, and does not invent answers.

Use it for a board-meeting tracker, governance log, resolutions register, or board risk register. It fits Growth stage in the Protect layer. A request can be:

Board actions from last year were never followed up.

It creates empty templates and supplies process guidance. It provides no automation, reminders, or synchronization, and does not calculate payroll, tax, leave, or KPIs. It cannot replace company secretarial duties or qualified legal governance advice.

The sixteen-field base list includes Board Item, Item Type, Meeting Date, Agenda, Presented By, Decision, Resolution Number, Vote Result, Action Owner, Due Date, Risk Level, Linked Report, Documents, Confidential, Status, and Board Item ID. Linked Report is a relation; meeting and due dates are dates. Item types include resolutions, actions, risks, agenda, minutes, and updates. Risk options span Low to Critical, confidentiality spans Public to Highly Restricted, and statuses run from Proposed to Closed.

Requested CSV, SQL DDL, JSON Schema, and Notion mapping share one list. Excel-compatible CSV uses UTF-8 with a byte order mark and needs date formatting after import. A workbook requires a specific request; examples must be explicitly requested and synthetic.

Additional decision rules separate agenda items, resolutions, votes, conflicts, and follow-up actions. Quorum is a meeting fact; a recommendation is an opinion. Attendance or an unrecorded majority must not be used to infer approval. Capture confirmed motion wording, proposer, applicable seconder, voting method, abstentions, recusals, result, and effective date. Actions link to their originating resolution and have one accountable owner. Leave due dates empty when none was set, rather than filling them to satisfy the base template.

Board packs distinguish draft, circulated, approved, and superseded versions. Their index records document owner, version, confidentiality, circulation date, and approval state. Decision papers retain the decision requested, options, assumptions, conflicts, and adopted resolution. Minutes record chair, attendance, quorum, apologies, declarations, motions, vote counts, recusals, and close time. Circulated corrections create a new version and preserve superseded evidence; approved minutes are not overwritten with drafts. Folder proximity does not authorize wider disclosure of confidential papers.

Notion output goes to notion-manual-import. Relations require imported target databases; manual mappings need no connection. Live writes require verified access, target, authorization, and successful tool evidence.

Sensitive review information should be minimized and generated templates kept empty.