0
0
Source

/em -board-prep — Board Meeting Preparation

Install

mkdir -p .claude/skills/board-prep && curl -L -o skill.zip "https://mcp.directory/api/skills/download/5308" && unzip -o skill.zip -d .claude/skills/board-prep && rm skill.zip

Installs to .claude/skills/board-prep

About this skill

/em:board-prep — Board Meeting Preparation

Command: /em:board-prep <agenda>

Prepare for the adversarial version of your board, not the friendly one. Every hard question they'll ask. Every number you need cold. The narrative that acknowledges weakness without losing the room.


The Reality of Board Meetings

Your board members have seen 50+ companies. They've watched founders flinch at their own numbers, spin bad news as "learning opportunities," and present sanitized decks that hide what's actually happening.

They know when you're not being straight with them. The question isn't whether they'll ask the hard questions — it's whether you're ready for them.

The best board meetings aren't the ones where everything looks good. They're the ones where the CEO demonstrates they see reality clearly, have a plan, and can execute under pressure.


The Preparation Framework

Phase 1: Numbers Cold

Before the meeting, every number in your deck should live in your head, not just the slide.

The numbers you must know without looking:

  • Current MRR / ARR and month-over-month growth rate
  • Burn rate (monthly) and runway (months at current burn)
  • Headcount by department
  • CAC and LTV by channel / segment
  • Net Revenue Retention
  • Pipeline: value, conversion rate, average sales cycle
  • Churn: rate, top reasons, top churned accounts
  • Gross margin (product), net margin (company)
  • Key hiring positions open and time-to-fill

Stress test yourself: Can you answer "what's your burn?" without hesitation? "What's your churn rate by segment?" If you pause, you don't know it.

Phase 2: Anticipate the Hard Questions

For every item on the agenda, generate the adversarial version of the question.

Standard adversarial questions by topic:

Revenue performance:

  • "You missed revenue by 20% this quarter. What specifically failed?"
  • "Is this a pipeline problem, a conversion problem, or a capacity problem?"
  • "If you missed because of one big deal, how dependent is your model on individual deals?"
  • "When do you project recovery and what are the leading indicators you're right?"

Runway / burn:

  • "At current burn you have N months. What's your plan if the next round takes 9 months?"
  • "What would you cut first if you had to extend runway by 6 months today?"
  • "Is there a scenario where you don't raise another round?"

Product / roadmap:

  • "You shipped X. What did customers actually do with it?"
  • "What did you kill this quarter and why?"
  • "Where are you behind on roadmap? What's slipping?"

Team:

  • "Who's at risk of leaving? How would that affect execution?"
  • "You've had 3 VP-level hires not work out. What pattern do you see?"
  • "Is the team the right team for this stage?"

Competition:

  • "Competitor Y just raised $50M. How does that change your position?"
  • "If they copy your best feature in 90 days, what's your moat?"

Phase 3: Build the Narrative

The board meeting isn't a status update. It's a leadership demonstration.

The structure that works:

  1. Where we are (honest) — Current state of business, the real number, not the smoothed one
  2. What we learned — What the data is telling us that we didn't know 90 days ago
  3. What we got wrong — Name it directly. Don't make them ask.
  4. What we're doing about it — Specific, dated, owned actions
  5. What we need from this room — Concrete ask. Not "support" — specific introductions, decisions, resources.

The rule on bad news: Never let the board be surprised. If a quarter went badly, they should know before the deck. A 5-sentence email 3 days before: "Revenue came in at $X vs $Y target. Here's what happened, here's what I'm doing, here's what I need from you."

Phase 4: Adversarial Preparation

Do a mock board meeting. Have someone play the hardest director you have.

The simulation:

  • Present your deck as you would
  • The mock director asks every uncomfortable question
  • You answer without referring to the deck
  • After: note every question that made you pause or feel defensive

The questions that made you defensive = the questions you need to prepare for.

Phase 5: Director-by-Director Prep

Not all board members want the same thing from a meeting.

For each director, know:

  • Their primary concern right now (usually tied to their investment thesis)
  • The metric they watch most closely
  • What would make them lose confidence in you
  • What they've said in the last meeting that you should address

Common director types:

  • The operator — wants to know what's breaking and who owns fixing it
  • The financial investor — focused on path to profitability or next raise
  • The strategic investor — worried about competitive position and moat
  • The independent — watching governance, team dynamics, and your judgment

Pre-Meeting Checklist

48 hours before:

  • All numbers verified against source systems (not last week's export)
  • Deck reviewed for internal consistency
  • Pre-read sent to board (deck + 1-page brief on key topics)
  • One-on-ones done with any director likely to have concerns
  • 3 hardest questions you expect — rehearsed out loud

Day of meeting:

  • Agenda with time allocations distributed
  • Know the ask for each agenda item (decision needed, input wanted, FYI)
  • Materials to leave behind prepared
  • Follow-up action template ready

During the Meeting

What the board is watching:

  • Do you own the bad news or deflect it?
  • Are you defending a narrative or sharing reality?
  • Do you know your numbers or do you look things up?
  • When challenged, do you get defensive or engage?
  • Do you know what you don't know?

The single best thing you can do: Name the hard thing before they do. "I want to address the revenue miss directly. Here's what happened, here's what I should have caught earlier, here's what changes."


After the Meeting

Within 24 hours:

  • Send action items with owners and dates
  • Send any data you promised but didn't have
  • Note the questions that came up you weren't ready for
  • Schedule follow-up with any director who seemed unsatisfied

The next board prep starts now.

senior-architect

alirezarezvani

Comprehensive software architecture skill for designing scalable, maintainable systems using ReactJS, NextJS, NodeJS, Express, React Native, Swift, Kotlin, Flutter, Postgres, GraphQL, Go, Python. Includes architecture diagram generation, system design patterns, tech stack decision frameworks, and dependency analysis. Use when designing system architecture, making technical decisions, creating architecture diagrams, evaluating trade-offs, or defining integration patterns.

170129

content-creator

alirezarezvani

Create SEO-optimized marketing content with consistent brand voice. Includes brand voice analyzer, SEO optimizer, content frameworks, and social media templates. Use when writing blog posts, creating social media content, analyzing brand voice, optimizing SEO, planning content calendars, or when user mentions content creation, brand voice, SEO optimization, social media marketing, or content strategy.

11619

cold-email

alirezarezvani

When the user wants to write, improve, or build a sequence of B2B cold outreach emails to prospects who haven't asked to hear from them. Use when the user mentions 'cold email,' 'cold outreach,' 'prospecting emails,' 'SDR emails,' 'sales emails,' 'first touch email,' 'follow-up sequence,' or 'email prospecting.' Also use when they share an email draft that sounds too sales-y and needs to be humanized. Distinct from email-sequence (lifecycle/nurture to opted-in subscribers) — this is unsolicited outreach to new prospects. NOT for lifecycle emails, newsletters, or drip campaigns (use email-sequence).

3713

content-trend-researcher

alirezarezvani

Advanced content and topic research skill that analyzes trends across Google Analytics, Google Trends, Substack, Medium, Reddit, LinkedIn, X, blogs, podcasts, and YouTube to generate data-driven article outlines based on user intent analysis

10913

ceo-advisor

alirezarezvani

Executive leadership guidance for strategic decision-making, organizational development, and stakeholder management. Includes strategy analyzer, financial scenario modeling, board governance frameworks, and investor relations playbooks. Use when planning strategy, preparing board presentations, managing investors, developing organizational culture, making executive decisions, or when user mentions CEO, strategic planning, board meetings, investor updates, organizational leadership, or executive strategy.

8413

content-humanizer

alirezarezvani

Makes AI-generated content sound genuinely human — not just cleaned up, but alive. Use when content feels robotic, uses too many AI clichés, lacks personality, or reads like it was written by committee. Triggers: 'this sounds like AI', 'make it more human', 'add personality', 'it feels generic', 'sounds robotic', 'fix AI writing', 'inject our voice'. NOT for initial content creation (use content-production). NOT for SEO optimization (use content-production Mode 3).

359

You might also like

flutter-development

aj-geddes

Build beautiful cross-platform mobile apps with Flutter and Dart. Covers widgets, state management with Provider/BLoC, navigation, API integration, and material design.

643969

drawio-diagrams-enhanced

jgtolentino

Create professional draw.io (diagrams.net) diagrams in XML format (.drawio files) with integrated PMP/PMBOK methodologies, extensive visual asset libraries, and industry-standard professional templates. Use this skill when users ask to create flowcharts, swimlane diagrams, cross-functional flowcharts, org charts, network diagrams, UML diagrams, BPMN, project management diagrams (WBS, Gantt, PERT, RACI), risk matrices, stakeholder maps, or any other visual diagram in draw.io format. This skill includes access to custom shape libraries for icons, clipart, and professional symbols.

591705

ui-ux-pro-max

nextlevelbuilder

"UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient."

318398

godot

bfollington

This skill should be used when working on Godot Engine projects. It provides specialized knowledge of Godot's file formats (.gd, .tscn, .tres), architecture patterns (component-based, signal-driven, resource-based), common pitfalls, validation tools, code templates, and CLI workflows. The `godot` command is available for running the game, validating scripts, importing resources, and exporting builds. Use this skill for tasks involving Godot game development, debugging scene/resource files, implementing game systems, or creating new Godot components.

339397

nano-banana-pro

garg-aayush

Generate and edit images using Google's Nano Banana Pro (Gemini 3 Pro Image) API. Use when the user asks to generate, create, edit, modify, change, alter, or update images. Also use when user references an existing image file and asks to modify it in any way (e.g., "modify this image", "change the background", "replace X with Y"). Supports both text-to-image generation and image-to-image editing with configurable resolution (1K default, 2K, or 4K for high resolution). DO NOT read the image file first - use this skill directly with the --input-image parameter.

451339

fastapi-templates

wshobson

Create production-ready FastAPI projects with async patterns, dependency injection, and comprehensive error handling. Use when building new FastAPI applications or setting up backend API projects.

304231

Stay ahead of the MCP ecosystem

Get weekly updates on new skills and servers.