devskill 2.0.7 → 2.0.8

package/skills/gtm-board-and-investor-communication/SKILL.md

@@ -0,0 +1,456 @@
+---
+name: gtm-board-and-investor-communication
+description: 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.
+license: MIT
+metadata:
+  author: Smit Patel (https://linkedin.com/in/smitkpatel)
+  source: https://github.com/beingsmit/technical-product-gtm
+---
+
+# 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 members read dozens of updates. The Three Things model gives them a mental filing system: momentum (feel good), risk (pay attention), agency (this team handles problems). Without it, boards either over-index on one bad metric or miss the real issue buried in a 40-slide deck.
+
+---
+
+### 3. Progress Is Directional, Not Absolute
+
+**The Pattern:**
+
+It doesn't matter if you hit 100K users if you were aiming for 50K — or if you missed 200K. Context is everything. Show progress toward your goal, not just the number.
+
+**How to Frame Progress:**
+
+- **On track:** "Target 100K active developers. Currently 70K. All initiatives performing as planned. Confidence: High."
+- **At risk:** "Target 100K active developers. Currently 50K. Acquisition cost higher than expected. Testing new channels. Adjusted target: 85K. Confidence: Medium."
+- **Ahead:** "Target 100K active developers. Currently 95K. Exceeding acquisition forecasts. New partnerships accelerating growth. Confidence: Very high."
+
+**The Rules:**
+1. Set the goal upfront (every metric needs a target)
+2. Show progress as % toward goal, not just absolute number
+3. Acknowledge misses; explain pivots
+4. State confidence level based on trajectory
+
+**Common Mistake:**
+
+Changing goals when you miss them. Boards track this. If Q1 target was 100K and you hit 60K, don't make Q2 target 75K and call it "revised guidance." State the miss, explain why, show the recovery plan. Credibility compounds faster than metrics.
+
+---
+
+### 4. The Four-Tier Metric Hierarchy
+
+**The Pattern:**
+
+Too many metrics confuse the board. Too few miss important signals. Structure your metrics in four tiers, and never change them quarter to quarter.
+
+**Tier 1: North Star (1 metric)**
+The single metric that best represents company health.
+- Examples: ARR, active users, tasks completed
+- Show trend line, not just current state
+- This is the one metric the board should remember if they forget everything else
+
+**Tier 2: Driver Metrics (3-5 metrics)**
+Leading indicators that predict your north star.
+- User acquisition rate
+- Retention curves (how many active last month remain active this month?)
+- Feature adoption (% of users on key feature)
+- DAU/MAU ratio
+- Pipeline coverage
+- Why track these: early warning before revenue impact
+
+**Tier 3: Health Metrics (3-5 metrics)**
+Signals of team and operational health.
+- Burn rate and runway
+- Headcount vs plan
+- Engineering velocity / shipping pace
+- NPS or customer satisfaction
+- Why track these: capacity constraints on growth
+
+**Tier 4: Red Flags (2-3 thresholds)**
+Metrics that, if they cross a threshold, require immediate action.
+- Churn rate above X%
+- CAC above $Y
+- Retention decline greater than Z%
+- Why track these: triggers for strategic conversation, not just monitoring
+
+**The Discipline Rules:**
+
+1. **Same metrics every quarter.** Build a 4-6 quarter track record. OK to add new metrics, but never drop old ones.
+2. **One context sentence per metric.** What does this metric tell us? Is it good or bad? What's the implication?
+3. **Actuals vs plan, always.** Never show a metric without showing what you planned. The delta is the conversation.
+4. **Disaggregate when needed.** Total usage hides segments. Break down by customer type, segment, product line — wherever averages mask reality.
+5. **Use health indicators.** Green/yellow/red status for quick board assessment. Lets board scan the dashboard and zoom in on yellows and reds.
+
+**Common Mistake:**
+
+Changing which metrics you show based on which ones look good this quarter. Boards notice immediately. It's the fastest way to lose credibility on your numbers. Show the same dashboard every time — when a metric looks bad, that's the conversation.
+
+---
+
+### 5. Deliver Bad News Before the Board Asks
+
+**The Pattern:**
+
+Board confidence erodes when bad news is delayed or sugar-coated. They can handle bad news. They can't handle surprises. And they hate slow decision-making.
+
+**The Pre-Brief Pattern:**
+
+Before bad news hits the full board, pre-brief your lead director 48-72 hours before the meeting.
+
+- **Who:** Board chair or most experienced director
+- **What:** The issue, your assessment, your plan
+- **Why:** Director can help frame for the full board, avoid surprise shock, and may have seen this pattern before
+
+Then send a short email to the full board:
+
+"Wanted to flag something before our next meeting. [Specific problem]. Here's what we know so far, what we don't know yet, and what we're doing about it. Will have a full update at the board meeting."
+
+**The Bad News Framework:**
+
+For every piece of bad news, four elements:
+
+1. **What happened** (specific, one sentence — not defensive)
+   - "We missed Q1 target of 10 new enterprise customers; achieved 7"
+
+2. **Why it happened** (root cause, not excuse)
+   - "Customer evaluation timelines slipped due to product gaps we didn't diagnose early enough"
+   - Own it: "We misread the demand signal" not "the market shifted"
+
+3. **What's the impact** (honest about severity)
+   - "Affects Q1 ARR by ~$50K, pushing us below original guidance"
+
+4. **What we're doing about it** (specific actions, owners, timeline)
+   - "Changed sales motion to qualify on product readiness upfront; revised Q2 target to 15 (including Q1 backlog of 7)"
+
+**How NOT to Communicate a Miss:**
+- "We didn't hit Q1 goals, but the pipeline is strong"
+- "External factors slowed deals, but we're confident about Q2"
+- "We had some implementation challenges, but they're resolved now"
+
+All vague. All defensive. None explain root cause or plan.
+
+**Follow-Through Pattern:**
+
+Every subsequent board update should reference previously raised issues: "Last quarter I flagged [issue]. Here's the update: [progress]. Status: [resolved / in progress / escalating]."
+
+This builds a track record of follow-through. Boards remember who tracks their own problems.
+
+**Common Mistake:**
+
+Sandwiching bad news between good news hoping nobody notices. Board members see this immediately. It damages trust more than the bad news itself.
+
+---
+
+### 6. The Monthly Investor Update
+
+**The Pattern:**
+
+Most founders send investor updates quarterly at best. The best founders send monthly — even when things are bad. Especially when things are bad.
+
+**Why Monthly:**
+- Keeps investors engaged without scheduling calls
+- When you need help (intros, advice, bridge), investors already have context
+- Consistency signals operational discipline; irregular updates signal chaos
+
+**The Format:**
+
+**Subject line:** [Company Name] — [Month] Update
+
+**Opening (1 paragraph):**
+One headline. Brief context.
+
+**TL;DR (3 bullets):**
+- One number (the metric that matters most right now)
+- One win (specific — customer name, deal size, milestone)
+- One challenge (with what you're doing about it)
+
+**Key Metrics (same table every month):**
+
+| Metric | This Month | Last Month | 3-Mo Avg | vs Plan |
+|--------|-----------|------------|----------|---------|
+| ARR | | | | |
+| MRR Growth | | | | |
+| Burn Rate | | | | |
+| Runway (months) | | | | |
+| Pipeline | | | | |
+| Customers | | | | |
+
+Don't include metrics unchanged from last update — focus on what's new.
+
+**Key Updates (2-3 bullets):**
+- Major hires, product launches, partnership/customer wins
+- Strategic pivots or course corrections
+- Specific enough to matter
+
+**Asks (1-2 bullets):**
+- What help do you need? Intros, hiring leads, strategic advice
+- Be specific: "Looking for intro to VP Eng at [company type]" not "Looking for engineering talent"
+
+**The Cadence Rules:**
+- Same day every month. First Monday, last Friday — pick one and never miss it
+- Send within a week of major news (don't hold it for the next scheduled update)
+- During active fundraising: weekly updates to warm investors, monthly to existing
+
+**Common Mistake:**
+
+Only sending updates when things are good. Six months of good news followed by silence tells investors exactly what you're not telling them.
+
+---
+
+### 7. Burn Is About Discipline; Revenue Is About Traction
+
+**The Pattern:**
+
+Financial communication to the board has two separate stories. Don't conflate them.
+
+**Burn Communication:**
+- Monthly rate, runway in months, YoY improvement
+- Efficiency gains (what did you cut, what did you optimize?)
+- Capital plan: what's secured, what's targeted, what's the timeline
+
+The burn story is: "We are disciplined operators who make capital go further."
+
+**Revenue Communication:**
+- MoM growth, CAC, LTV, payback period
+- Customer segmentation (self-serve vs enterprise, what's the mix?)
+- Monetization plan with timeline
+
+The revenue story is: "We have traction and know how to grow it."
+
+**Reconcile Both:**
+The best financial communication shows: "We're burning less while growing faster." That's evidence of operating leverage, and it's the single most compelling thing a board can hear.
+
+**Common Mistake:**
+
+Conflating burn with growth. A board that hears "we're growing fast" while burn rate climbs thinks you're buying growth. A board that hears "we cut burn by 40%" while growth stalls thinks you're in survival mode. Tell both stories, separately, and then connect them.
+
+---
+
+### 8. Cascading Strategy from Board to Organization
+
+**The Pattern:**
+
+Strategy decided in a board room doesn't matter if the team doesn't know it. Create a systematic communication cascade.
+
+**The Four Levels:**
+
+**Level 1: Executive Team (Weekly)**
+- Strategic priorities and emerging risks
+- Key decisions needing alignment
+
+**Level 2: Extended Leadership (Bi-weekly)**
+- How strategy impacts each function
+- Key priorities and how success will be measured
+
+**Level 3: All-Hands (Monthly, 60 min)**
+- Leadership update (15 min): where we are, what's changed
+- Wins celebration (10 min): customers, launches, people
+- Deep dive (20 min): one strategic initiative in detail
+- Q&A (15 min): real questions, real answers
+
+**Level 4: Team-Specific (Ongoing)**
+- How team goals connect to company strategy
+- What success looks like for this team specifically
+
+**The Test:**
+
+Pick a random employee. Can they explain the company strategy? If not, the cascade is broken. Strategy that exists only in executive heads is not strategy — it's a secret.
+
+**Connect OKRs to Cascade:**
+- Company OKRs from strategy
+- Function OKRs aligned to company
+- Team OKRs aligned to function
+- Individual understands how they contribute
+
+**Common Mistake:**
+
+Inconsistent messaging. If different leaders tell different stories about where the company is headed, the organization optimizes for conflicting goals. Write the strategy down. One page. Make everyone use the same words.
+
+---
+
+## Decision Trees
+
+### Board Meeting vs Investor Update
+
+```
+Is this a full board meeting?
+├─ Yes → Full structure: pre-read + Three Things + decisions + deep dive
+└─ No → Continue...
+    │
+    Is this a major event (fundraise close, big miss, key hire)?
+    ├─ Yes → Ad-hoc update immediately (don't wait for schedule)
+    └─ No → Monthly investor update format
+```
+
+### How to Frame a Metric
+
+```
+Did you hit the target?
+├─ Yes → State it, move on. Don't over-celebrate.
+└─ No → Continue...
+    │
+    Do you understand why?
+    ├─ Yes → Root cause + plan + revised timeline
+    └─ No → Say "we're diagnosing" + what you're doing to find out
+        │
+        Is the miss material (affects runway, strategy, or board confidence)?
+        ├─ Yes → Pre-brief lead director before board meeting
+        └─ No → Include in Three Things narrative, "what's not working"
+```
+
+---
+
+## Common Mistakes
+
+**1. Board meetings as status reports**
+Board members can read. Send the pre-read. Use the meeting for decisions and discussion, not data walkthroughs.
+
+**2. Changing metrics every quarter**
+Consistency in metrics builds trust. The moment you swap out a metric that looked bad for one that looks good, you've told the board your numbers can't be trusted.
+
+**3. No clear ask**
+Every investor update, every board meeting should have an ask. Intros, advice, approval, patience. Investors want to help — if you never ask, they disengage.
+
+**4. Defending instead of describing**
+When you're explaining away a miss for 10 minutes, the board hears defensiveness. State the miss, state the cause, state the plan. Move on.
+
+**5. Strategy stays in the board room**
+If your team can't explain the strategy, you haven't communicated it. Cascade it or it doesn't exist.
+
+**6. Surprises in the board meeting**
+Bad news should never land for the first time in a board meeting. Pre-brief the lead director. Send the flag email. Let the board process before the meeting.
+
+---
+
+## Quick Reference
+
+**Board meeting flow:**
+Pre-read (48-72 hrs before) → Questions (15 min) → Three Things narrative (15 min) → Decision items (30-45 min) → Deep dive (20-30 min) → Closed session (10 min)
+
+**Three Things model:**
+What's working + What's not + What we're doing about it
+
+**Metric hierarchy:**
+North star (1) → Drivers (3-5) → Health (3-5) → Red flags (2-3 thresholds)
+
+**Bad news protocol:**
+Pre-brief lead director (48-72 hrs) → Flag email to full board → What happened → Why → Impact → Plan → Follow up every subsequent meeting
+
+**Monthly investor update:**
+TL;DR (3 bullets) → Same metrics table → Key updates (2-3) → Specific asks (1-2)
+
+**Communication cascade:**
+Exec (weekly) → Leadership (bi-weekly) → All-hands (monthly) → Team (ongoing)
+
+---
+
+## Related Skills
+
+- **operating-cadence**: Internal meeting rhythms that feed board preparation
+- **enterprise-account-planning**: Pipeline and deal metrics for board reporting
+- **technical-product-pricing**: Pricing decisions that require board input
+
+---
+
+*Based on preparing and supporting board communications across multiple companies from Series A through post-IPO — building the deck and sitting in the room at some, reporting updates to the board at others. Includes the investor update cadence that maintained trust through missed quarters, the "Three Things" narrative model used across multiple companies, and the metric discipline framework that survived years of hypergrowth. Not theory — patterns from being close enough to the board to see what lands and what doesn't.*

package/skills/gtm-board-and-investor-communication/SYNC.md

@@ -0,0 +1,5 @@
+# Sync Info
+
+- **Source:** `vendor/awesome-copilot/skills/gtm-board-and-investor-communication`
+- **Git SHA:** `23fb7006c132a0bba75b0e5af7a35cab11272812`
+- **Synced:** 2026-03-24

package/skills/gtm-developer-ecosystem/LICENSE.md

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright GitHub, Inc.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.