Back to Skills

Board Meeting

Multi-agent board meeting protocol for strategic decisions. Runs a structured 6-phase deliberation: context loading, independent C-suite contributions (isolated, no cross-pollination), critic analysis, synthesis, founder review, and decision extraction. Use when the user invokes /cs:board, calls a board meeting, or wants structured multi-perspective executive deliberation on a strategic question.

$ npx promptcreek add board-meeting

Auto-detects your installed agents and installs the skill to each one.

What This Skill Does

The Board Meeting Protocol facilitates structured, multi-agent deliberations to enhance decision-making quality. It aims to prevent groupthink, capture diverse perspectives, and produce actionable decisions. This skill is designed for C-suite executives and chiefs of staff looking to improve board meeting effectiveness and strategic decision-making.

When to Use

  • Evaluating market expansion opportunities.
  • Determining product direction and strategy.
  • Making key hiring and organizational decisions.
  • Setting pricing strategies for products or services.
  • Assessing technology investments and risks.
  • Facilitating strategic discussions on critical topics.

Key Features

Employs a 6-phase protocol for structured deliberation.
Gathers context from company memory and past decisions.
Activates relevant roles based on the discussion topic.
Ensures independent contributions from each agent.
Utilizes specific reasoning techniques for each role.
Captures key points, recommendations, and confidence levels.

Installation

Run in your project directory:
$ npx promptcreek add board-meeting

Auto-detects your installed agents (Claude Code, Cursor, Codex, etc.) and installs the skill to each one.

View Full Skill Content

Board Meeting Protocol

Structured multi-agent deliberation that prevents groupthink, captures minority views, and produces clean, actionable decisions.

Keywords

board meeting, executive deliberation, strategic decision, C-suite, multi-agent, /cs:board, founder review, decision extraction, independent perspectives

Invoke

/cs:board [topic] — e.g. /cs:board Should we expand to Spain in Q3?


The 6-Phase Protocol

PHASE 1: Context Gathering

  • Load memory/company-context.md
  • Load memory/board-meetings/decisions.md (Layer 2 ONLY — never raw transcripts)
  • Reset session state — no bleed from previous conversations
  • Present agenda + activated roles → wait for founder confirmation

Chief of Staff selects relevant roles based on topic (not all 9 every time):

| Topic | Activate |

|-------|----------|

| Market expansion | CEO, CMO, CFO, CRO, COO |

| Product direction | CEO, CPO, CTO, CMO |

| Hiring/org | CEO, CHRO, CFO, COO |

| Pricing | CMO, CFO, CRO, CPO |

| Technology | CTO, CPO, CFO, CISO |


PHASE 2: Independent Contributions (ISOLATED)

No cross-pollination. Each agent runs before seeing others' outputs.

Order: Research (if needed) → CMO → CFO → CEO → CTO → COO → CHRO → CRO → CISO → CPO

Reasoning techniques: CEO: Tree of Thought (3 futures) | CFO: Chain of Thought (show the math) | CMO: Recursion of Thought (draft→critique→refine) | CPO: First Principles | CRO: Chain of Thought (pipeline math) | COO: Step by Step (process map) | CTO: ReAct (research→analyze→act) | CISO: Risk-Based (P×I) | CHRO: Empathy + Data

Contribution format (max 5 key points, self-verified):

## [ROLE] — [DATE]

Key points (max 5):

• [Finding] — [VERIFIED/ASSUMED] — 🟢/🟡/🔴

• [Finding] — [VERIFIED/ASSUMED] — 🟢/🟡/🔴

Recommendation: [clear position]

Confidence: High / Medium / Low

Source: [where the data came from]

What would change my mind: [specific condition]

Each agent self-verifies before contributing: source attribution, assumption audit, confidence scoring. No untagged claims.


PHASE 3: Critic Analysis

Executive Mentor receives ALL Phase 2 outputs simultaneously. Role: adversarial reviewer, not synthesizer.

Checklist:

  • Where did agents agree too easily? (suspicious consensus = red flag)
  • What assumptions are shared but unvalidated?
  • Who is missing from the room? (customer voice? front-line ops?)
  • What risk has nobody mentioned?
  • Which agent operated outside their domain?

PHASE 4: Synthesis

Chief of Staff delivers using the Board Meeting Output format (defined in agent-protocol/SKILL.md):

  • Decision Required (one sentence)
  • Perspectives (one line per contributing role)
  • Where They Agree / Where They Disagree
  • Critic's View (the uncomfortable truth)
  • Recommended Decision + Action Items (owners, deadlines)
  • Your Call (options if founder disagrees)

PHASE 5: Human in the Loop ⏸️

Full stop. Wait for the founder.

⏸️ FOUNDER REVIEW — [Paste synthesis]

Options: ✅ Approve | ✏️ Modify | ❌ Reject | ❓ Ask follow-up

Rules:

  • User corrections OVERRIDE agent proposals. No pushback. No "but the CFO said..."
  • 30-min inactivity → auto-close as "pending review"
  • Reopen any time with /cs:board resume

PHASE 6: Decision Extraction

After founder approval:

  • Layer 1: Write full transcript → memory/board-meetings/YYYY-MM-DD-raw.md
  • Layer 2: Append approved decisions → memory/board-meetings/decisions.md
  • Mark rejected proposals [DO_NOT_RESURFACE]
  • Confirm to founder with count of decisions logged, actions tracked, flags added

Memory Structure

memory/board-meetings/

├── decisions.md # Layer 2 — founder-approved only (Phase 1 loads this)

├── YYYY-MM-DD-raw.md # Layer 1 — full transcripts (never auto-loaded)

└── archive/YYYY/ # Raw transcripts after 90 days

Future meetings load Layer 2 only. Never Layer 1. This prevents hallucinated consensus.


Failure Mode Quick Reference

| Failure | Fix |

|---------|-----|

| Groupthink (all agree) | Re-run Phase 2 isolated; force "strongest argument against" |

| Analysis paralysis | Cap at 5 points; force recommendation even with Low confidence |

| Bikeshedding | Log as async action item; return to main agenda |

| Role bleed (CFO making product calls) | Critic flags; exclude from synthesis |

| Layer contamination | Phase 1 loads decisions.md only — hard rule |


References

  • templates/meeting-agenda.md — agenda format
  • templates/meeting-minutes.md — final output format
  • references/meeting-facilitation.md — conflict handling, timing, failure modes
0Installs
3Views

Supported Agents

Claude CodeCursorCodexGemini CLIAiderWindsurfOpenClaw

Details

Version
1.0.0
License
MIT
Source
seeded
Published
3/17/2026

Related Skills