Board Meeting
Multi-agent board meeting protocol for strategic decisions.
Before & after
Same prompt, same agent — the only difference is the skill.
That's a significant strategic question. There are good arguments on both sides - enterprise offers higher contract values but longer sales cycles, while SMB lets you move faster. It really depends on your current resources, competitive position, and revenue targets. I could help you think through the trade-offs by exploring your runway, technical capacity, and go-to-market capabilities. What's your current customer mix, and how much runway do you have? That would help me give you more targeted guidance on which direction makes sense.
BOARD DELIBERATION INITIATED PHASE 1: CONTEXT LOADING Current ARR $2.4M, 80% SMB, 20% enterprise. Runway 18 months. Engineering team: 4. Market: Saturated SMB, high-growth enterprise. PHASE 2: CFO CONTRIBUTION Enterprise path → higher ACV, longer payback. Estimated 12-month sales cycles. Initial revenue impact: negative 6 months, then +320% by month 18. Requires 2 additional sales hires. PHASE 3: VP SALES CONTRIBUTION SMB moat eroding. Competitors undercut pricing monthly. Enterprise procurement is blocked without SOC 2. We can obtain it in 8 weeks. Current win rate: 15%. Enterprise win rate benchmark: 8-12%. PHASE 4: CRITIC ANALYSIS Enterprise risk: sales-driven cost structure, long deal cycles kill velocity. SMB risk: margin compression, platform commoditization. Hybrid fails both. PHASE 5: SYNTHESIS Enterprise wins on defensibility and margin. Requires commitment: SOC 2, enterprise-grade support, sales team restructure. 18-month break-even. PHASE 6: FOUNDER DECISION RECOMMENDATION: Enterprise pivot. Start SOC 2 immediately. Hire 1 enterprise sales rep while maintaining SMB base at reduced focus.
About this skill
name: board-meeting description: Use when Multi-agent board meeting protocol for strategic decisions.
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:boardroom, calls a board meeting, or wants structured multi-perspective executive deliberation on a strategic question.
What you get
- Public GitHub repo (alirezarezvani/claude-skills)
- the board-meeting skill folder with SKILL.md. Part of a 337-skill / 30-agent / 70-command install.
Customize your output
- Fork the repo and adapt the skill's instructions and references to your workflow.
Example output
Activates automatically when your request matches Board Meeting; chains with the other skills, agents, and commands in the collection.
Best for
Creators, builders, and teams using Claude Code.
SKILL.md preview
---
name: board-meeting
description: Use this skill when running a structured, multi-perspective executive deliberation on a strategic question, or when the board meeting protocol is explicitly invoked.
version: 1.0.0
category: Business & Ops / Executive Advisory
author: AgentVolt
license: proprietary
tags:
- business-ops
- executive-advisory
---
# Board Meeting
Runs a structured six-phase deliberation protocol simulating a board meeting for strategic decisions, keeping each executive perspective isolated before synthesis.
## When to use
… (sign up to view the full skill)More business & ops skills
View all Business & Ops skills →Gc Review
/cs:gc-review <plan> — General Counsel interrogation of contracts, IP, regulatory, term sheets, and employment-law surface.
Caio Review
/cs:caio-review <plan> — Eval-demanding Chief AI Officer interrogation of any plan that involves AI: model selection, risk classification, cost economics, or AI hiring.
Boardroom
/cs:boardroom <brief> — 6-phase multi-role deliberation across the C-suite with Phase 2 isolation, critic pre-screen, and synthesis.
Context Engine
Loads and manages company context for all C-suite advisor skills.