Gtm-Board-And-Investor-Communication
Gtm-Board-And-Investor-Communication是一款writing方向的AI技能,核心价值是Board meeting preparation, investor updates, and executive communication,可用于解决开发者在writing领域的实际问题,帮助用户提升效率、自动化重复任务或优化工作流。
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 boar
mkdir -p ./skills/gtm-board-and-investor-communication && curl -sfL https://raw.githubusercontent.com/github/awesome-copilot/main/skills/gtm-board-and-investor-communication/SKILL.md -o ./skills/gtm-board-and-investor-communication/SKILL.md Run in terminal / PowerShell. Requires curl (Unix) or PowerShell 5+ (Windows).
Skill Content
# 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 Meeting Structure:**
**Pre-Read (Sent 48-72 Hours Before)**
- Financial dashboard (ARR, burn, runway, pipeline)
- Metric scorecard with health indicators (green/yellow/red)
- 2-3 page narrative summary covering market context and strategic update
- Rule: If it can be read, don't present it
**The Meeting (90-120 Minutes)**
1. **Market context and questions on pre-read** (15 min)
- What's changed in the market since last meeting?
- Board asks about anything unclear from pre-read
- No re-presenting the data
2. **CEO strategic update — The "Three Things"** (15 min)
- **What's working** (2-3 areas showing momentum)
- **What's not** (1-2 specific gaps, not vague)
- **What we're doing about it** (specific changes, not promises)
- This is narrative, not numbers
3. **Decision items** (30-45 min)
- 1-3 topics where the board's input or approval is needed
- Come prepared: "We're deciding between X and Y, board thoughts?"
- Leave with a decision, not "let's revisit next quarter"
4. **Deep dive** (20-30 min)
- One topic explored in depth (rotating each meeting)
- Bring the functional leader who owns it
- Examples: pricing strategy, competitive landscape, org design, market expansion
5. **Closing** (10 min)
- Summarize decisions made and action owners
- Closed session (board without management)
- CEO and board chair debrief
**Common Mistakes:**
- Opening with data before narrative (board gets lost in numbers without context)
- Multiple competing narratives (board can't synthesize — pick one arc)
- Trying to cover too many topics deeply (results in rushed decisions on everything)
- No deep dives (board becomes a rubber stamp)
- Filling the meeting with good news (boards don't trust CEOs who only share wins)
---
2. The "Three Things" Narrative Model
**The Pattern:**
Businesses are too complex to summarize in one headline. Three distinct points — what's working, what's not, what's changing — let the board grasp status and trajectory in minutes.
**What's Working (2-3 areas):**
Be specific. Not "sales are going well" but "closed first six-figure enterprise deal, validating the commercial motion." Quantify momentum:
- New product launches gaining adoption
- Sales motion maturing (first big customer, repeatable motion emerging)
- Community/ecosystem milestones
**What's Not Working (1-2 areas):**
Be equally specific. Not "we had some challenges" but "self-serve conversion is weak — strong awareness but 0.1% conversion rate." Board needs to understand the actual problem, not a euphemism.
**What We're Doing About It (for each "not working"):**
Articulate specific changes. What product changes? What org changes? What's the timeline? What resources are committed?
**Why This Works:**
Board membe
🎯 Best For
- UI designers
- Product designers
- Claude users
- GitHub Copilot users
- Content creators
💡 Use Cases
- Generating component mockups
- Creating design system tokens
- Content creation
- Style guide enforcement
📖 How to Use This Skill
- 1
Install the Skill
Copy the install command from the Terminal tab and run it. The SKILL.md file downloads to your local skills directory.
- 2
Load into Your AI Assistant
Open Claude or GitHub Copilot and reference the skill. Paste the SKILL.md content or use the system prompt tab.
- 3
Apply Gtm-Board-And-Investor-Communication to Your Work
Provide context for your task — paste source material, describe your audience, or share existing work to guide the AI.
- 4
Review and Refine
Edit the AI output for accuracy, tone, and completeness. Add human insight where the AI lacks context.
❓ Frequently Asked Questions
Does this work with Figma?
Some design skills integrate with Figma plugins. Check the Works With section for supported tools.
Can Gtm-Board-And-Investor-Communication maintain my brand voice?
Yes — provide style guides or example content in your prompt for consistent brand-aligned output.
How do I install Gtm-Board-And-Investor-Communication?
Copy the install command from the Terminal tab and run it. The skill downloads to ./skills/gtm-board-and-investor-communication/SKILL.md, ready to use.
Can I customize this skill for my team?
Absolutely. Edit the SKILL.md file to add team-specific instructions, examples, or workflows.
⚠️ Common Mistakes to Avoid
Skipping usability testing
AI-generated designs should be validated with real users before development.
Publishing unedited drafts
AI writing needs human editing for facts, flow, and authentic voice.