Individual skill
board-meeting-prep
Use this skill when a CEO, CRO, or GTM leader is preparing for a board meeting, investor meeting, or operating review and needs the room to decide something. Produces a decision-first pre-read, an in-room agenda budgeted for discussion, a single primary ask framed as a decision brief, and a Q&A and director preparation brief. Use it for "board deck", "board prep", "board pre-read", "what should I ask the board for", "presenting GTM to the board", "investment case for the board", "first board meeting as a new CRO", or "the board keeps asking why we are not growing faster".
skills/jason-mesiarik/board-meeting-prep/SKILL.md
Source commit 5d786aad0c7b2ca59b1abf1f601f9407ca261996
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 237
- Repository last updated
- Oct 20, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- leadership Declared skill tag
- revops Declared skill tag
- sales Declared skill tag
- sales Derived category
- finance Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 4,954 bytesreferences/altitude-and-qa.mddoc · 3,849 bytesreferences/decision-brief.mddoc · 4,168 bytesreferences/package-rubric.mddoc · 2,339 bytesreferences/pre-read-and-room.mddoc · 3,404 bytesreferences/standing-report.mddoc · 2,641 bytesreferences/worked-examples.mddoc · 4,258 bytes
Read excerpt
Applies whenever a leader has board, investor, or executive-committee time. Produces a pre-read that transfers context before the meeting and an agenda that spends the meeting on judgment.
**The doctrine:** a board deck transfers context before the meeting so the meeting can be spent exercising judgment. Everything below serves that sentence.
## The sequence
Build in this order. Never start with slides.
**Audience → Decision → Story → Evidence → Discussion → Commitment**
1. **Audience.** Name every director. For each, write the lens they will apply (portfolio benchmarking, capital efficiency, execution quality, governance, network) and the one question they are most likely to ask. Read `references/altitude-and-qa.md`.
2. **Decision.** Write the single primary decision the room must make. Then up to two secondary asks for advice or input. If no decision exists, the meeting is a report: send it as a memo. Read `references/decision-brief.md`.
3. **Story.** Write what the board must believe to say yes. Reduce it to three governing messages at most. Each message is a claim, not a topic.
4. **Evidence.** Under each message, place the evidence that makes it true. One conclusion per visual, stated in the title. Deep evidence goes to the appendix and is presented only when a director pulls it. Performance reporting follows the same fixed format every meeting: read `references/standing-report.md`.