board-pre-read

Featured

Write a board pre-read that's sent before the meeting so the meeting is about decisions, not status. Use when asked to prepare a board pre-read, a board update/package, or pre-meeting materials for a board. Produces a board pre-read — a TL;DR, the metrics dashboard vs. plan, what's working / what's not, the decisions and asks for the board, and risks — designed to be read in advance.

AI & Automation 1,228 stars 220 forks Updated today MIT

Install

View on GitHub

Quality Score: 96/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Board Pre-Read Skill The best board meetings spend zero time on status because the board already read it. A pre-read sent 48+ hours ahead does that: it conveys the state of the business and, crucially, tells the board exactly what input and decisions are needed — so the meeting is discussion and decisions, not a slide-reading session. This skill structures that document. ## Required Inputs Ask for these only if they aren't already provided: - **The headline** — the one thing the board should take away this period (good or bad). - **Metrics vs. plan** — the key numbers against the plan/forecast (revenue, growth, burn, runway, the north-star). - **What changed** — major wins, misses, and shifts since last meeting. - **Decisions/asks** — what you actually need from the board (approval, input, introductions). ## Output Format ### Board Pre-Read — [company], [month/quarter] **Sent:** [date, ≥48h before the meeting] **1. TL;DR** — 3–5 bullets: the state of the business, the headline, runway, and the decisions you're bringing. A busy board member should get the gist from this alone. **2. Metrics dashboard** — the core numbers vs. plan, with the trend and a one-line "so what" each. Show misses honestly — boards trust founders who surface bad news first. | Metric | This period | vs. plan | Trend | Note | |---|---|---|---|---| **3. What's working** — the 2–3 things going well and why (so they can be doubled down on). **4. What's not** — the 2–3 problems, what you're doing ...

Details

Author
mohitagw15856
Repository
mohitagw15856/pm-claude-skills
Created
5 months ago
Last Updated
today
Language
HTML
License
MIT

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category