From executive-mentor
Prepares for adversarial board meetings: key metrics to memorize cold, hard questions by agenda topic, and reality-facing narratives.
npx claudepluginhub stillquietlyloud/claude_skills --plugin executive-mentorThis skill uses the workspace's default tool permissions.
**Command:** `/em:board-prep <agenda>`
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
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.
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.
Before the meeting, every number in your deck should live in your head, not just the slide.
The numbers you must know without looking:
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.
For every item on the agenda, generate the adversarial version of the question.
Standard adversarial questions by topic:
Revenue performance:
Runway / burn:
Product / roadmap:
Team:
Competition:
The board meeting isn't a status update. It's a leadership demonstration.
The structure that works:
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."
Do a mock board meeting. Have someone play the hardest director you have.
The simulation:
The questions that made you defensive = the questions you need to prepare for.
Not all board members want the same thing from a meeting.
For each director, know:
Common director types:
48 hours before:
Day of meeting:
What the board is watching:
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."
Within 24 hours:
The next board prep starts now.