gtm-board-and-investor-communication
Board meeting preparation, investor updates, and executive communication. Use when preparing board decks, writing investor updates, handling bad news with the board, structuring QBRs, or building board-level metric discipline. Includes the "Three Things" narrative model, the 4-tier metric hierarchy, and the pre-brief pattern that prevents board surprises.
npx skills add github/awesome-copilot --skill gtm-board-and-investor-communication --agent copilot
Same command for any agent — swap --agent for claude-code, codex, cursor.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
The skill guides how to structure board meetings, investor updates, and executive communication to build trust and drive decisions. It prescribes a narrative-first approach (story, then data), a specific board meeting structure (pre-read, Three Things, decisions, deep dive, closing), and a set of patterns for communicating both good and bad news. It includes detailed templates such as the Pre-Read contents, The Three Things narrative model (What’s Working, What’s Not, What We’re Doing About It), the Four-Tier Metric Hierarchy, and the Bad News Pre-Brief pattern. It also defines patterns for monthly investor updates, cascading strategy, and how to frame progress versus targets. It provides explicit formats, cadence rules, and examples for communicating misses and progress with clarity.
How it works
- Use triggers like board meeting prep, investor updates, or handling misses to activate the guidance.
- Apply the narrative-first rule: open with the journey, then show data.
- Prepare a Pre-Read with a financial dashboard, metric scorecard, and a 2-3 page narrative summary; ensure things readable without presenting raw slides.
- Structure the board meeting into phases: Market context, CEO strategic update using The Three Things, Decision items, Deep dive, Closing.
- Employ The Three Things: What's Working, What's Not, What We're Doing About It, with explicit, specific items and timelines.
- Use The Four-Tier Metric Hierarchy to organize metrics into North Star, Driver Metrics, Health Metrics, and Red Flags, maintaining consistency across quarters.
- Deliver bad news before the board asks via the Pre-Brief pattern: inform the lead director 48-72 hours prior and send a concise board pre-brief email to the entire board.
- For monthly investor updates, follow the specified format: subject line, opening, TL;DR, Key Metrics (consistent table), Key Updates, and Asks, with cadence rules.
- Ensure follow-through in updates referencing prior issues with status and owners.
When to use it
- Triggers include questions like "How do I prepare for our board meeting?" and "What should go in our investor update?" and situations like missing targets or needing a board-friendly narrative.
- Context covers seed through growth-stage organizations, with emphasis on board-to-organization alignment, monthly/quarterly investor updates, and handling misses or strategic pivots.
What it can touch
- Tools: copilot
- It prescribes structured content, templates, and patterns for board decks, narratives, and updates; it does not specify executable code or scripts beyond narrative templates and formats.
Caveats
- License: MIT
- Sections rely on explicit patterns and avoid speculative outcomes; it emphasizes concrete, specific actions over generalized promises and prohibits changing targets without acknowledging misses.
- It enforces a consistent reporting discipline across quarters and warns against mixed messaging or over-optimistic framing that undermines credibility.
# Board and Investor Communication Structure board meetings, investor updates, and executive communication that builds trust and drives decisions — not slide decks that nobody reads. ## When to Use **Triggers:** - "How do I prepare for our board meeting?" - "What should go in our investor update?" - "We missed our numbers, how do we communicate this?" - "Board deck structure" - "How often should we update investors?" - "Our board meetings aren't productive" **Context:** - Seed through growth-stage companies - Board meeting preparation and follow-up - Monthly/quarterly investor updates - Handling misses and bad news - Cascading strategy from board to organization --- ## Core Frameworks ### 1. Tell the Story, Then Show the Data **The Pattern:** Most board meetings start with a data dump. Slide after slide of metrics, then 10 minutes of Q&A where board members try to figure out what it all means. Flip it. The narrative should lead; data should confirm. **How It Works:** Open with where you are in the journey. Not "here's our ARR" but "here's what we believed coming into the quarter, what we learned, and where that puts us now." Then show the data that validates the narrative. **Board
- When to Use
- Core Frameworks
- 1. Tell the Story, Then Show the Data
- 2. The "Three Things" Narrative Model
- 3. Progress Is Directional, Not Absolute
- 4. The Four-Tier Metric Hierarchy
- 5. Deliver Bad News Before the Board Asks
- 6. The Monthly Investor Update
- 7. Burn Is About Discipline; Revenue Is About Traction
- 8. Cascading Strategy from Board to Organization
- Decision Trees
- Board Meeting vs Investor Update
- How to Frame a Metric
- Common Mistakes
What does the gtm-board-and-investor-communication skill do?
Board meeting preparation, investor updates, and executive communication. Use when preparing board decks, writing investor updates, handling bad news with the board, structuring QBRs, or building board-level metric discipline. Includes the "Three Things" narrative model, the 4-tier metric hierarchy, and the pre-brief pattern that prevents board surprises.
How do I install it?
Run `npx skills add github/awesome-copilot --skill gtm-board-and-investor-communication --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From github/awesome-copilot, a repository with 37,432 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.