New: Earn 20% as an AgentAlley affiliate. Share your link and earn on every sale you refer. Join now New: Earn 20% as an affiliate. Join now

Board meeting preparation for the adversarial scenario

/em:board-prep — Board Meeting Preparation

by alirezarezvani · MIT license · ★ 26,349 on GitHub · updated Aug 30

/em:board-prep — Board Meeting Preparation cover

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.

---
name: "board-prep"
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."
---

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

Overview

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.

Manual install (npx, ZIP)
Claude Codenpx skills add alirezarezvani/claude-skills --skill board-prep -g -a claude-code
Claude Code (manual)mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/alirezarezvani/claude-skills/tar.gz/19392f7a0826 \ | tar -xz -C ~/.claude/skills --strip-components=4 claude-skills-19392f7a0826/c-level-advisor/executive-mentor/skills/board-prep
Windows (PowerShell)New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/b067898d287140943dbd/board-prep.zip" -OutFile "$env:TEMP\board-prep.zip"; Expand-Archive "$env:TEMP\board-prep.zip" -DestinationPath "$HOME\.claude\skills" -Force
Claude.ai / desktopDownload the ZIP and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md6.5 KB
Read the files here
alirezarezvani/19392f71 file
SKILL.md
Show the full text157 lines

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

1---
2name: "board-prep"
3description: "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."
4---
5 
6# /em:board-prep — Board Meeting Preparation
7 
8**Command:** `/em:board-prep <agenda>`
9 
10Prepare 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.
11 
12---
13 
14## The Reality of Board Meetings
15 
16Your 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.
17 
18They 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.
19 
20The 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.
21 
22---
23 
24## The Preparation Framework
25 
26### Phase 1: Numbers Cold
27 
28Before the meeting, every number in your deck should live in your head, not just the slide.
29 
30**The numbers you must know without looking:**
31- Current MRR / ARR and month-over-month growth rate
32- Burn rate (monthly) and runway (months at current burn)
33- Headcount by department
34- CAC and LTV by channel / segment
35- Net Revenue Retention
36- Pipeline: value, conversion rate, average sales cycle
37- Churn: rate, top reasons, top churned accounts
38- Gross margin (product), net margin (company)
39- Key hiring positions open and time-to-fill
40 
41**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.
42 
43### Phase 2: Anticipate the Hard Questions
44 
45For every item on the agenda, generate the adversarial version of the question.
46 
47**Standard adversarial questions by topic:**
48 
49*Revenue performance:*
50- "You missed revenue by 20% this quarter. What specifically failed?"
51- "Is this a pipeline problem, a conversion problem, or a capacity problem?"
52- "If you missed because of one big deal, how dependent is your model on individual deals?"
53- "When do you project recovery and what are the leading indicators you're right?"
54 
55*Runway / burn:*
56- "At current burn you have N months. What's your plan if the next round takes 9 months?"
57- "What would you cut first if you had to extend runway by 6 months today?"
58- "Is there a scenario where you don't raise another round?"
59 
60*Product / roadmap:*
61- "You shipped X. What did customers actually do with it?"
62- "What did you kill this quarter and why?"
63- "Where are you behind on roadmap? What's slipping?"
64 
65*Team:*
66- "Who's at risk of leaving? How would that affect execution?"
67- "You've had 3 VP-level hires not work out. What pattern do you see?"
68- "Is the team the right team for this stage?"
69 
70*Competition:*
71- "Competitor Y just raised $50M. How does that change your position?"
72- "If they copy your best feature in 90 days, what's your moat?"
73 
74### Phase 3: Build the Narrative
75 
76The board meeting isn't a status update. It's a leadership demonstration.
77 
78**The structure that works:**
79 
801. **Where we are (honest)** — Current state of business, the real number, not the smoothed one
812. **What we learned** — What the data is telling us that we didn't know 90 days ago
823. **What we got wrong** — Name it directly. Don't make them ask.
834. **What we're doing about it** — Specific, dated, owned actions
845. **What we need from this room** — Concrete ask. Not "support" — specific introductions, decisions, resources.
85 
86**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."
87 
88### Phase 4: Adversarial Preparation
89 
90Do a mock board meeting. Have someone play the hardest director you have.
91 
92**The simulation:**
93- Present your deck as you would
94- The mock director asks every uncomfortable question
95- You answer without referring to the deck
96- After: note every question that made you pause or feel defensive
97 
98**The questions that made you defensive = the questions you need to prepare for.**
99 
100### Phase 5: Director-by-Director Prep
101 
102Not all board members want the same thing from a meeting.
103 
104**For each director, know:**
105- Their primary concern right now (usually tied to their investment thesis)
106- The metric they watch most closely
107- What would make them lose confidence in you
108- What they've said in the last meeting that you should address
109 
110**Common director types:**
111- **The operator** — wants to know what's breaking and who owns fixing it
112- **The financial investor** — focused on path to profitability or next raise
113- **The strategic investor** — worried about competitive position and moat
114- **The independent** — watching governance, team dynamics, and your judgment
115 
116---
117 
118## Pre-Meeting Checklist
119 
120**48 hours before:**
121- [ ] All numbers verified against source systems (not last week's export)
122- [ ] Deck reviewed for internal consistency
123- [ ] Pre-read sent to board (deck + 1-page brief on key topics)
124- [ ] One-on-ones done with any director likely to have concerns
125- [ ] 3 hardest questions you expect — rehearsed out loud
126 
127**Day of meeting:**
128- [ ] Agenda with time allocations distributed
129- [ ] Know the ask for each agenda item (decision needed, input wanted, FYI)
130- [ ] Materials to leave behind prepared
131- [ ] Follow-up action template ready
132 
133---
134 
135## During the Meeting
136 
137**What the board is watching:**
138- Do you own the bad news or deflect it?
139- Are you defending a narrative or sharing reality?
140- Do you know your numbers or do you look things up?
141- When challenged, do you get defensive or engage?
142- Do you know what you don't know?
143 
144**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."
145 
146---
147 
148## After the Meeting
149 
150Within 24 hours:
151- Send action items with owners and dates
152- Send any data you promised but didn't have
153- Note the questions that came up you weren't ready for
154- Schedule follow-up with any director who seemed unsatisfied
155 
156The next board prep starts now.
157 
View all files on GitHub →

Details

Updated
Aug 30, 2026
License
MIT
Stars on the repo
★ 26,349
Checked
Source
alirezarezvani/claude-skills ↗
Creator
alirezarezvani · 363 listings
View creator

Similar skills

See all →
SkillCreate stunning, animation-rich HTML presentationsFrontend slideszarazhangrui/frontend-slides · by zarazhangruiCreate stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Use when the user wants to build a presentation, convert a PPT/PPTX to web, or create slides for a talk/pitch. Helps non-designers discover their aesthetic through visual exploration rather than abstract choices.★ 30.3k GitHub starsSkillCreate professional, dark-themed SVG diagrams of any typeDiagram GeneratorJimLiu/baoyu-skills · by JimLiuCreate professional, dark-themed SVG diagrams of any type — architecture diagrams, flowcharts, sequence diagrams, structural diagrams, mind maps, timelines, illustrative/conceptual diagrams, and more. Use this skill whenever the user asks for any kind of technical or conceptual diagram, visualization of a system, process flow, data flow, component relationship, network topology, decision tree, org chart, state machine, or any visual representation of structure/logic/process. Also trigger when the user says "画个图" "画一个架构图" "diagram" "flowchart" "sequence diagram" "draw me a ..." or uploads content and asks to visualize it. Output is always a standalone .svg file.★ 26.6k GitHub starsSkillGenerate self-contained HTML visual explanations for systemsVisual explainernicobailon/visual-explainer · by nicobailonGenerate self-contained HTML visual explanations for systems, code changes, plans, data, and technical concepts. Use for diagrams, architecture overviews, diff or plan reviews, project recaps, comparison tables, slide decks, animated explainers, and other visual explanations.★ 10.2k GitHub starsSkillHTML PPT Studio — author professional static HTMLhtml-ppt — HTML PPT Studiolewislulu/html-ppt-skill · by lewisluluHTML PPT Studio — author professional static HTML presentations in many styles, layouts, and animations, all driven by templates. Use when the user asks for a presentation, PPT, slides, keynote, deck, slideshow, "幻灯片", "演讲稿", "做一份 PPT", "做一份 slides", a reveal-style HTML deck, a 小红书 图文, or any kind of multi-slide pitch/report/sharing document that should look tasteful and be usable with keyboard navigation. Triggers include keywords like "presentation", "ppt", "slides", "deck", "keynote", "reveal", "slideshow", "幻灯片", "演讲稿", "分享稿", "小红书图文", "talk slides", "pitch deck", "tech sharing", "technical presentation".★ 8.6k GitHub starsSkillProfessional logo and brand-mark designLogo designkaankiziltug/logo-design-skill · by kaankiziltugProfessional logo and brand-mark design, from brief to production files. Guides discovery and the design brief, concept generation, choosing a mark type (wordmark, monogram, letterform, pictorial, abstract, emblem, mascot, combination), building clean geometric SVG logos, optical refinement, colour and typography, testing (16 px, one-colour, reversed, shelf test), client presentation, delivery variants and brand guidelines. Includes a searchable library of 1,400+ real-world SVG logos classified by type, technique, geometry and industry, plus scripts that audit SVGs and generate test sheets, presentation boards and export variants. Use this skill whenever the user wants a logo, logotype, wordmark, monogram, brand mark, symbol, app icon or favicon designed, redesigned, refreshed, critiqued or compared; asks for logo ideas or concepts; needs a design brief, logo guidelines, lockups or an identity system; or mentions branding a new company, product, app or project — even if they don't say the word "logo".★ 2.8k GitHub starsSkillDraws a code change or partPR Lenscoldteadotai/pr-lens · by coldteadotaiWHAT: Draws a code change or part of a codebase as an animated architecture or data-flow diagram, on its own or in a pull request. WHEN: asked to diagram, visualise or explain a change or a system, or when a pull request should carry a diagram. KEYWORDS: PR Lens, diagram, architecture, data flow, visualise, visualize, pull request★ 1.9k GitHub stars

More from alirezarezvani

SkillResume a paused experiment/ar:ar-resume — Resume Experimentalirezarezvani/claude-skills · by alirezarezvaniResume a paused experiment. Checkout the experiment branch, read results history, continue iterating. Use when the user runs /ar:ar-resume or asks to pick up a previously started autoresearch experiment.★ 26.3k GitHub starsSkillShow experiment dashboard with results, active loops/ar:ar-status — Experiment Dashboardalirezarezvani/claude-skills · by alirezarezvaniShow experiment dashboard with results, active loops, and progress. Use when the user runs /ar:ar-status or asks how an autoresearch experiment is going.★ 26.3k GitHub starsSkillStart an autonomous experiment loop with user-selected/ar:loop — Autonomous Experiment Loopalirezarezvani/claude-skills · by alirezarezvaniStart an autonomous experiment loop with user-selected interval (10min, 1h, daily, weekly, monthly). Uses CronCreate for scheduling. Use when the user runs /ar:loop or asks to run an autoresearch experiment continuously on a schedule.★ 26.3k GitHub starsSkillRun a single experiment iteration/ar:run — Single Experiment Iterationalirezarezvani/claude-skills · by alirezarezvaniRun a single experiment iteration. Edit the target file, evaluate, keep or discard. Use when the user runs /ar:run or asks for one manual autoresearch iteration.★ 26.3k GitHub starsSkillSet up a new autoresearch experiment interactively/ar:setup — Create New Experimentalirezarezvani/claude-skills · by alirezarezvaniSet up a new autoresearch experiment interactively. Collects domain, target file, eval command, metric, direction, and evaluator. Use when the user runs /ar:setup or asks to start optimizing a file with the autoresearch loop.★ 26.3k GitHub starsSkill/cs:boardroom <brief/cs:boardroom — Multi-Role Boardroom Deliberationalirezarezvani/claude-skills · by alirezarezvani/cs:boardroom <brief> — 6-phase multi-role deliberation across the C-suite with Phase 2 isolation, critic pre-screen, and synthesis. Outputs a board memo. Use when a decision spans multiple executive domains — e.g. a pricing change touching finance, positioning, and product, or a raise-vs-cut runway call.★ 26.3k GitHub stars