C-Level Advisory BoardStrategyProtocol

Board Meeting

Multi-agent board meeting protocol for strategic decisions.

$skillfish add ~skills/board-meeting

Capabilities Real Examples Get Started Models & Context

What This Skill Can Do

Concrete capabilities you get when you install this skill.

Design board agenda structure for strategic, operational, and governance meetings

Facilitate multi-agent debate and decision-making across C-suite and board members

Synthesize and document board decisions with owner, rationale, and timeline

Prepare pre-board alignment briefs and supporting materials

Track board action items and follow-through between meetings

Navigate conflict and strong disagreements among board members

Real Conversations

See how the Board Meeting skill responds to actual requests. These are representative examples of what your AI agent will produce.

You

Convene the board. Topic: whether to raise a Series B now or cut to default alive and grow sustainably. We're at $3.8M ARR, 12% MoM growth, $195K/month burn, 14 months runway. Our Series A investors want us to raise. I'm not sure I want to take on more dilution and pressure. Run the board session.

Agent

Board Meeting convened. Topic: Series B vs. Default Alive

CEO opening: $3.8M ARR, 12% MoM, $195K burn, 14 months runway. The raise question is live.

CFO Advisor: The math first. At 12% MoM, you're at $8.4M ARR in 12 months without any additional investment. Default alive is achievable — you need to reach ~$330K MRR before burn exceeds revenue, which at current growth is ~9 months out. However, cutting to default alive from $195K burn likely means 15–20% headcount reduction, which risks slowing growth to 6–8% MoM. At 6% MoM, you don't reach default alive in 14 months — you run out. The cut-to-default-alive path has its own execution risk.

CRO Advisor: The fundraise market context: Series B valuations for 12% MoM SaaS companies are in the $30–40M range today. In 12 months, at $8M ARR and continued growth, that range is $50–70M. Waiting and continuing to grow creates a better raise — but only if you don't run into a market downturn or competitive pressure that slows growth. The timing asymmetry favors waiting if growth holds.

CEO Advisor: The founder's concern about dilution and pressure is legitimate, not just emotional. Series B brings a new board member, quarterly reporting to 2–3 institutional investors, and implicit expectation of Series C in 24 months. If your personal vision for this company is a $30M ARR profitable business, the venture path is misaligned. Clarify the destination before making a capital decision.

Board recommendation: Conditional raise strategy. Soft-process with 3–4 Series B funds over the next 60 days without committing. If you get term sheets above $38M pre-money, evaluate seriously. If market conditions are unfavorable, run to default alive with surgical cuts. Avoid the binary either/or framing.

You

Emergency board session. Salesforce just acquired our biggest competitor (Meridian, $140M deal) at 7:00 AM this morning. We're at $2.9M ARR directly competing with Meridian in the mid-market segment. We have 127 customers who chose us over Meridian. Get all advisors on this.

Agent

Emergency Board Session — Salesforce/Meridian Acquisition Response

CEO Advisor (strategic framing): This is a threat and an opportunity simultaneously. Acquisitions of this type typically cause 18–24 months of product confusion for the acquired company. Meridian's roadmap, pricing, and GTM will shift to align with Salesforce's enterprise motion. Their mid-market customers — including the ones who chose them over you — are now questioning whether they're on the right platform. The next 90 days are a land-grab window.

CMO Advisor (positioning response): Activate immediately. Key message: "Built for mid-market teams, not absorbed into enterprise platforms." Create a dedicated landing page today: "Thinking about what Salesforce's acquisition means for your Meridian contract?" Run targeted LinkedIn campaigns to Meridian customer job titles. This is not opportunistic — it's responsive. Budget: authorize $15–25K in immediate paid spend.

CRO Advisor (customer and pipeline action): Two urgent priorities: (1) Send a proactive communication to your 127 customers this week — not promotional, reassuring. Confirm your independence, roadmap commitment, and dedicated mid-market focus. (2) Pull all open deals where Meridian appeared in competitive notes and contact those prospects today. Acquisition uncertainty is a proven accelerant for prospects who were on the fence.

CFO Advisor (strategic options): This acquisition also raises your own M&A profile. If Salesforce paid 50x revenue for Meridian, your current ARR suggests a $145M acquisition value at similar multiples. That creates inbound interest. Decide now whether you're open to that conversation or want to stay independent — because the calls will come in the next 30 days.

COO Advisor (operational readiness): Stress-test your onboarding capacity. If CMO's campaign works and you get 30–40 new demos in the next 30 days, can you convert and onboard them without degrading current customer experience? If not, prioritize onboarding capacity before paid spend.

Get Started

How to install and use this skill in your preferred environment.

Skills are designed for AI coding agents (Claude Code, Cursor, Windsurf) and IDE-based workflows where the agent can read files, run scripts, and act on your codebase. Web-based AI can use the knowledge and frameworks, but won't have tool access.

Models & Context

Which AI models and context windows work best with this skill.

Recommended Models

Best

Claude Opus 4 Claude Sonnet 4 GPT-4.1 Gemini 2.5 Pro Grok 3 Kimi K2

Good

Claude Haiku 4.5 GPT-4.1 mini Gemini 2.5 Flash Grok 3 mini

Larger models produce more detailed, production-ready outputs.

Context Window

This skill's SKILL.md is typically 3–10 KB — fits in any modern context window.

8K Skill only

32K+ Skill + conversation

100K+ Skill + references + codebase

All current frontier models (Claude, GPT, Gemini) support 100K+ context. Use the full window for complex multi-service work.

Pro tips for best results

1

Be specific

Include numbers — users, budget, RPS — so the skill can size the architecture.

2

Share constraints

Compliance needs, team size, and existing stack all improve the output.

3

Iterate

Start with a high-level design, then ask follow-ups for IaC, cost analysis, or security review.

4

Combine skills

Pair with companion skills below for end-to-end coverage.

Ready to try Board Meeting?

Install the skill and start getting expert-level guidance in your workflow — any agent, any IDE.