board-deck-generator
Generates professional board meeting presentation content (board-deck.md) with executive summary, financials, product updates, GTM metrics, team/hiring, strategic decisions, and appendix. Supports early-stage, growth-stage, and pre-IPO formats. Use when preparing board meeting materials, quarterly board updates, or investor presentations.
git clone --depth 1 https://github.com/OneWave-AI/claude-skills /tmp/board-deck-generator && cp -r /tmp/board-deck-generator/board-deck-generator ~/.claude/skills/board-deck-generatorSKILL.md
# 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.
Audit websites for accessibility issues and WCAG compliance. Use when checking accessibility, fixing a11y issues, or ensuring WCAG compliance.
Deploy a 2-layer parallel agent hierarchy for large, parallelizable work — big refactors, multi-file migrations, codebase-wide audits, bulk generation. Layer 1 is 3-50+ specialist agents, each with its own full context window; Layer 2 is 2+ sub-agents per member. Includes git safety, tiered sizing, a pre-deploy gate, phantom-completion checks, and multi-wave follow-up.
Deploys swarms of sub-agents for massive parallel data processing tasks. Unlike agent-army (which is for code changes), this is for DATA tasks -- processing 1000 documents, analyzing datasets, bulk content generation. Configurable swarm size, task distribution, result aggregation, progress tracking, and error recovery.
Designs and deploys custom agent teams for specific business workflows. Interactive discovery of business processes, then generates complete team configurations with specialized agent roles, tool access, communication protocols, and handoff rules.
Agent-to-Agent (A2A) communication protocol. Connect two or more Claude agents that pass messages, share context, delegate tasks, and collaborate. Implements structured handoffs, shared memory, and multi-agent conversations.
Assesses how ready a business is for AI adoption across six dimensions. Evaluates data maturity, tech stack, team skills, process documentation, budget, and culture. Generates a comprehensive ai-readiness-report.md with scores, gap analysis, and recommended starting points. Aligned with OneWave AI's audit methodology.
Generate animated videos and motion graphics from natural language descriptions. Creates a standalone Vite + React project with Framer Motion scenes that auto-play in the browser. Use when the user wants to create animations, motion graphics, video intros, animated presentations, or product demos.
Generate comprehensive API documentation including endpoint descriptions, request/response examples, authentication guides, error codes, and SDKs. Creates OpenAPI/Swagger specs, REST API docs, and developer-friendly reference materials. Use when users need to document APIs, create technical references, or write developer documentation.