Skip to main content
ClaudeWave
Skill963 repo starsupdated 3d ago

board-deck-narrative

The board-deck-narrative skill constructs a complete narrative arc and slide-by-slide structure for board presentations, moving beyond topic lists to deliver specific talking points, content guidance, and presenter notes. Use this when building quarterly board updates, annual reviews, special board meetings, or fundraise-related presentations where a cohesive storyline and clear decision triggers are required.

Install in Claude Code
Copy
git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills /tmp/board-deck-narrative && cp -r /tmp/board-deck-narrative/plugins/pm-business/skills/board-deck-narrative ~/.claude/skills/board-deck-narrative
Then start a new Claude Code session; the skill loads automatically.

SKILL.md

# Board Deck Narrative Skill

This skill builds the complete narrative and slide structure for a board presentation — from opening framing to closing asks. It produces slide-by-slide content guidance, not just a list of topics.

## Required Inputs

Ask the user for these if not provided:
- **Company stage and context** (Seed / Series A / Growth — and where you are in the year)
- **Board meeting type** (Regular quarterly / Annual / Special / Fundraise-related)
- **Key themes for this meeting** (e.g. strong growth quarter / pivoting strategy / hiring challenge / fundraise update)
- **Key metrics to feature**
- **Decisions needed from the board** (if any)
- **Time available** (e.g. 60 min / 90 min)
- **Audience** (investors only / investors + independent directors / mixed)

## Output Structure

---

# Board Deck Narrative: [Company] — [Quarter/Period]

**Meeting type:** [Regular quarterly / Special]
**Time:** [X minutes]
**Narrative theme:** [The one-sentence story of this quarter — e.g. "We hit our revenue target, but activation is the problem we need to solve together."]

---

## Opening Frame (Slide 1–2)

**Slide 1: Title**
- Company name, quarter, date
- One-sentence framing of the meeting's narrative arc

**Slide 2: Agenda**
- List of sections + time allocation
- Flag which sections need board input vs. are informational

*Presenter note: Board members are busy. Tell them in the first 2 minutes what you need from them today. It changes how they listen.*

---

## Business Performance (Slides 3–6, ~15 min)

**Slide 3: Scorecard / KPI Dashboard**
- Content: Key metrics vs. targets for the quarter. No more than 6 metrics.
- Format: Traffic-light table (Green / Amber / Red against plan)
- Narrative: [1–2 sentences — the headline story of the quarter in numbers]
- *Don't hide reds. Boards lose trust when they discover hidden problems later.*

**Slide 4: Revenue / Growth Deep Dive**
- Content: Revenue breakdown by segment, cohort retention, growth drivers
- Key message: [What the data shows about the health of growth]
- Call out: [Any trend that needs board context or discussion]

**Slide 5: Unit Economics**
- Content: CAC, LTV, payback period, gross margin — vs. last quarter and vs. plan
- Flag: Any metric moving in the wrong direction and what's causing it

**Slide 6: Operational Highlights**
- Content: 3–5 bullet points of the most significant things that happened this quarter
- Format: Each bullet = outcome, not activity. ("Signed 3 enterprise contracts worth £400K ARR" not "Continued enterprise sales motion")

---

## Strategic Update (Slides 7–9, ~15 min)

**Slide 7: Strategy Snapshot**
- Content: Where you said you'd be vs. where you are against the annual plan
- Narrative: [Honest assessment — what's on track, what's shifted and why]

**Slide 8: Key Strategic Decision or Update**
- Content: The one strategic topic that most needs board input this meeting
- Format: Context → Options considered → Recommendation → Question for board
- *This is the highest-value 10 minutes of the meeting. Frame it as a real question.*

**Slide 9: Product & Roadmap (if relevant)**
- Content: Top 3 product bets this quarter — what shipped, what's coming, why these bets
- Tailored for: What the board needs to understand to support strategic decisions, not a sprint review

---

## People & Organisation (Slide 10, ~5 min)

**Slide 10: Team Update**
- Content: Headcount (start vs. end of quarter), key hires made, open roles, any org changes
- Flag: Any people risks or leadership gaps the board should know about
- *Don't skip this slide. Board members often have network value here.*

---

## Financial Update (Slides 11–12, ~10 min)

**Slide 11: P&L Summary**
- Content: Revenue, gross margin, opex by category, EBITDA/net burn — actual vs. budget
- Include: Year-to-date vs. annual plan

**Slide 12: Cash & Runway**
- Content: Cash on hand, monthly burn rate, runway at current burn
- Include: Scenario if burn increases (e.g. key hire made), scenario if growth accelerates
- Flag immediately: If runway is < 18 months — this needs board awareness and planning

---

## Closing & Asks (Slides 13–14, ~10 min)

**Slide 13: Priorities for Next Quarter**
- Content: Top 3–5 priorities and what success looks like for each
- Format: Priority | What we're doing | How we'll know it worked
- *Keeps board accountability consistent across meetings*

**Slide 14: Board Asks**
- Content: Specific things you need from board members before next meeting
- Format: Each ask = specific, named if possible ("Looking for an intro to [Company] — [Board member X], do you have a connection?")
- *A board meeting without specific asks is a missed opportunity*

---

## Appendix (Optional)

- Detailed cohort analysis
- Competitive landscape update
- Full P&L
- Team org chart
- Any supporting data referenced in the main deck

*Appendix slides are available but not presented. Board members who want detail can ask.*

---

## Narrative Principles

- **Lead with honesty.** If it was a hard quarter, say so in the first slide. Don't bury bad news after the wins.
- **One slide = one idea.** If a slide has two messages, split it.
- **Fewer slides, more depth.** A 14-slide deck presented well beats a 35-slide deck rushed through.
- **Every slide has a "so what."** A slide that just shows data without a takeaway wastes board time.
- **Leave time for discussion.** Board value is in the conversation, not the presentation. Aim to spend 40% of the meeting presenting and 60% in discussion.

## Quality Checks

- [ ] Opening frame states the meeting's narrative theme
- [ ] Scorecard slide uses traffic-light format (not just green metrics)
- [ ] Strategic decision slide frames a real question for the board
- [ ] Financial slide includes runway explicitly
- [ ] Board asks are specific and actionable
- [ ] Deck is ≤ 15 slides (excluding appendix)

## Anti-Patterns

- [ ] Do not bury bad news after slides full of good news — boards lose trust when they discover problems w
ai-ethics-reviewSkill

Conduct a structured ethical review of an AI or ML feature, model, or product. Use when preparing to deploy an AI system, assessing algorithmic risk, auditing a model for bias, or producing a responsible AI impact assessment. Produces a structured ethics review covering fairness, transparency, privacy, safety, accountability, and societal impact with a risk tier score, pre-deployment checklist, and prioritised mitigations.

ai-product-canvasSkill

Structure AI and ML product decisions with the rigour of any product decision. Use when building AI-powered features, evaluating LLM integrations, designing AI products, or assessing AI readiness. Produces a complete AI product canvas covering problem definition, model approach, data requirements, evaluation framework, UX design, responsible AI checklist, and launch monitoring plan.

design-handoff-briefSkill

Transform feature briefs into structured design briefs that give designers the context they need before opening Figma. Use when asked to write a design brief, create a design handoff, brief a designer on a new feature, or translate a PRD into design requirements. Produces a brief with user goal, emotional context, success criteria, constraints, edge cases, and out-of-scope boundaries.

experiment-designerSkill

Design statistically rigorous A/B tests and interpret experiment results. Use when asked to design an experiment, run an A/B test, calculate sample size, interpret test results, or assess whether an experiment was successful. Produces a complete experiment design with hypothesis, sample size, run time, success criteria, and risk flags — or a results interpretation with ship/iterate/kill recommendation.

multi-source-signal-synthesiserSkill

Synthesises user signals from multiple research sources into a unified, weighted insight brief. Use when you have data from interviews, support tickets, NPS verbatims, app reviews, or sales calls and need to reconcile contradictions, surface the underlying need behind requests, or answer 'what are users really telling us'. Produces ranked insights with confidence ratings, source weighting rationale, divergent signal analysis by user segment, and a research gap identification section.

data-analysis-standardSkill

Structure a product data analysis, metric deep-dive, funnel analysis, or cohort study. Use when asked to analyse product metrics, investigate a drop in conversion, explain a data change to stakeholders, or find the root cause of a metric movement. Produces a structured analysis with question, root cause, confidence level, and recommended action.

product-health-analysisSkill

Interpret product metrics against goals and surface actionable signals. Use when asked to analyse product health, review key metrics, investigate a performance issue, produce a health report, or assess product-market fit signals. Produces a structured health report with RAG status, trend analysis, root cause hypotheses, and prioritised actions.

retention-analysisSkill

Structure a retention analysis, churn investigation, or engagement deep-dive for any product team. Use when asked to analyse user retention, investigate churn, measure DAU/MAU, or build a retention improvement plan. Produces a retention snapshot with root cause hypotheses, aha-moment correlation, and prioritised interventions.