board-pre-read
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.
git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills /tmp/board-pre-read && cp -r /tmp/board-pre-read/plugins/pm-business/skills/board-pre-read ~/.claude/skills/board-pre-readSKILL.md
# 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 about them, and where you want the board's help. Candour here is the whole game. **5. Decisions & asks** — explicit: "We're asking the board to approve X" / "We'd value input on Y" / "We need intros to Z." Tie each to the agenda. **6. Risks & watch-items** — the top risks to the plan and runway, and the leading indicators you're watching. **Appendix** — detail, financials, and supporting data (linked, not inline). ## Quality Checks - [ ] It's genuinely a pre-read — sent ahead, readable without a presenter - [ ] The TL;DR stands alone for a time-pressed director - [ ] Metrics are shown vs. plan, with misses surfaced honestly (not buried) - [ ] The decisions/asks for the board are explicit and tied to the agenda - [ ] Runway and the top risks are stated plainly ## Anti-Patterns - [ ] Do not save bad news for the live meeting — boards punish surprises; lead with the hard numbers - [ ] Do not send a deck to be read aloud — a pre-read is prose/dashboards designed for solo reading - [ ] Do not omit the asks — if the board doesn't know what you need, the meeting defaults to status theatre - [ ] Do not vanity-metric the dashboard — show the numbers that govern the business, against plan - [ ] Do not inline 40 pages of appendix — link the detail; keep the core pre-read tight ## Based On Board-management practice — pre-circulated reading, metrics-vs-plan transparency, and decision-focused agendas.
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.
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.
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.
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.
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.
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.
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.
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.