Skip to content
cccskills
FreePublished on GitHub

board-prep

Prepare for board meetings, investor updates, and fundraising presentations by reviewing key numbers, rehearsing difficult questions, and shaping an honest business narrative. Includes preparation for individual directors and follow-up actions after the meeting.

OriginalShow the original description

Board meeting preparation for the adversarial scenario, not the friendly one. Forces numbers-cold mastery, anticipates hard questions, builds a narrative that acknowledges weakness without losing the room. Use when preparing for a board meeting, an investor update, fundraising presentation, or any high-stakes adversarial review where every number must live in your head not just on a slide.

See how to install

Good for

  • Rehearsing difficult questions before a board meeting
  • Preparing key metrics for an investor update
  • Explaining missed targets and corrective actions
  • Organizing meeting decisions and follow-up actions

Files included (1)

  • SKILL.md6.5 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

/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.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

a11y-audit

FreeSummary

Audit web applications for accessibility issues against WCAG 2.2 Level A and AA, the web accessibility standards. Get framework-specific code fixes, contrast checks, verification steps, and reports, with options for automated checks in development pipelines.

  • Audit a web application before release
  • Fix contrast and keyboard navigation issues
  • Prepare accessibility reports for stakeholders
alirezarezvani/claude-skills28.4KUpdated Aug 30, 2026

ab-test-setup

FreeSummary

Plan A/B tests that compare page variations, from headlines to pricing layouts. Define a hypothesis, choose success metrics, calculate sample size and duration, and prepare launch checks and results reports to support decisions.

  • Comparing landing page headlines
  • Testing signup button changes
  • Planning pricing page experiments
alirezarezvani/claude-skills28.4KUpdated Aug 30, 2026

ad-creative

FreeSummary

Create paid ad headlines and body copy tailored to each platform's character limits. Use existing performance data to develop variations, explore new messaging angles, and check copy for length, quality, and potential rejection risks.

  • Creating Google RSA headlines
  • Writing Meta and LinkedIn ad copy
  • Developing variations of successful ads
alirezarezvani/claude-skills28.4KUpdated Aug 30, 2026

Review code changes from three critical perspectives: production failures, maintainability, and security. Get a consolidated report that ranks findings by severity and provides merge guidance, helping examine assumptions that an ordinary self-review may overlook.

  • Reviewing a pull request before merging
  • Getting a second opinion on AI-written code
  • Checking authentication or data access code
alirezarezvani/claude-skills28.4KUpdated Aug 30, 2026

aeo

FreeSummary

Audit and improve content intended for citation in AI answers. Review evidence, author information, and structure, generate revised content and structured metadata, and keep a local record of observed citations across AI services.

  • Audit existing articles for evidence and credibility gaps
  • Revise article structure and references for AI answers
  • Record citations observed across AI services
alirezarezvani/claude-skills28.4KUpdated Aug 30, 2026

Create signed records for consequential agent actions such as deployments, deletions, and payments. Decide which actions need evidence, record the agent, action, target, and policy, then verify the resulting certificate offline to detect later changes.

  • Creating signed records for production deployments
  • Preserving evidence of deletions and payments
  • Recording access grants for later review
alirezarezvani/claude-skills28.4KUpdated Aug 30, 2026

See all skills by alirezarezvani

Report a problem with this skill