board-deck-generator

Files (5)

• SKILL.md
• document-structure.md · references/
• examples.md · references/
• stage-templates.md · references/
• style-guide.md · references/

SKILL.md (first lines)

# Board Deck Generator

Generate institutional-quality `board-deck.md` content: concise, data-driven, honest about challenges, and focused on the decisions that need board input. Output must be ready for a CEO to present directly or hand to a design team for slide conversion.

## Contents

- `references/document-structure.md` -- The required 12-section deck structure with all tables and templates.
- `references/stage-templates.md` -- Early-stage, growth-stage, and pre-IPO emphasis and per-section additions.
- `references/style-guide.md` -- Formatting rules, tone and voice, quality checklist, common mistakes.
- `references/examples.md` -- A fully worked board ask.

## Inputs

Collect from the user. If critical inputs are missing, ask before generating. For non-critical gaps, insert bracketed placeholders like `[INSERT Q3 REVENUE]`.

Required:
- Company name and stage (early-stage / growth-stage / pre-IPO)
- Reporting period (e.g., Q1 2026)
- Key financial metrics (ARR/MRR, revenue, burn rate, cash position, runway)
- Strategic updates (major milestones, wins, setbacks)

Optional: detailed P&L, product roadmap, GTM metrics, hiring plan, customer logos/NPS, competitive changes, specific board asks, prior board deck, cap table, prior-quarter OKRs.

## Workflow

1. Identify the stage (early-stage, growth-stage, or pre-IPO) from user input. See `references/stage-templates.md`.
2. Collect and review all provided metrics, updates, and context.
3. Flag gaps. Ask the user for missing critical data; mark missing non-critical data with `[PLACEHOLDER]` notation.
4. If the user provides a prior board deck, read it first to maintain continuity in metric tracking, formatting, and narrative threads.
5. Build the full document following the section order in `references/document-structure.md`, applying the stage-appropriate emphasis from `references/stage-templates.md`.
6. Populate every table, narrative, and analysis using provided inputs.
7. Add analysis: explain what numbers mean, why they changed, and what to do about them. Do not just report.
8. Draft board asks with options, management recommendation, specific request, and timeline. See `references/examples.md`.
9. Apply formatting and tone from `references/style-guide.md`; run the quality checklist there before finalizing.
10. Write the completed deck to `board-deck.md` in the current working directory (or a user-specified path). Confirm the file path after writing.

From OneWave-AI/claude-skills, MIT.

More from OneWave-AI/claude-skills