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.
Best use case
board-meeting is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using board-meeting should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/board-meeting/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How board-meeting Compares
| Feature / Agent | board-meeting | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
Top AI Agents for Productivity
See the top AI agent skills for productivity, workflow automation, operational systems, documentation, and everyday task execution.
SKILL.md Source
# 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 1. Load `memory/company-context.md` 2. Load `memory/board-meetings/decisions.md` **(Layer 2 ONLY — never raw transcripts)** 3. Reset session state — no bleed from previous conversations 4. 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
Related Skills
onboarding-cro
When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," or "new user experience." For signup/registration optimization, see signup-flow-cro. For ongoing email sequences, see email-sequence.
codebase-onboarding
Codebase Onboarding
clipboard-knowledge-capture
把剪贴板片段沉淀到本地知识库,自动补来源、标签和后续行动。;use for clipboard, knowledge, capture workflows;do not use for 保存敏感密钥明文, 忽略来源信息.
board-prep
/em -board-prep — Board Meeting Preparation
cs-onboard
Founder onboarding interview that captures company context across 7 dimensions. Invoke with /cs:setup for initial interview or /cs:update for quarterly refresh. Generates ~/.claude/company-context.md used by all C-suite advisor skills.
board-deck-builder
Assembles comprehensive board and investor update decks by pulling perspectives from all C-suite roles. Use when preparing board meetings, investor updates, quarterly business reviews, or fundraising narratives. Covers structure, narrative framework, bad news delivery, and common mistakes.
youtube-watcher
Fetch and read transcripts from YouTube videos. Use when you need to summarize a video, answer questions about its content, or extract information from it.
youtube-transcript
Fetch and summarize YouTube video transcripts. Use when asked to summarize, transcribe, or extract content from YouTube videos. Handles transcript fetching via residential IP proxy to bypass YouTube's cloud IP blocks.
youtube-auto-captions - YouTube 自动字幕
## 描述
youtube
YouTube Data API integration with managed OAuth. Search videos, manage playlists, access channel data, and interact with comments. Use this skill when users want to interact with YouTube. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway).
yahoo-finance
Get stock prices, quotes, fundamentals, earnings, options, dividends, and analyst ratings using Yahoo Finance. Uses yfinance library - no API key required.
xurl
A Twitter research and content intelligence skill focused on attracting WordPress and Shopify clients. Use to analyze Twitter profiles, threads, and conversations for: (1) Identifying what small agency founders and eCommerce brands are discussing; (2) Understanding pain points around WordPress performance, Shopify CRO, and development bottlenecks; (3) Extracting high-performing content angles; (4) Turning insights into authority-building posts; (5) Converting Twitter intelligence into business leverage for clear content angles, strong positioning, and qualified inbound leads.