From ai-adoption-playbook
Drafts formatted AI section for board updates from results data, ensuring every paragraph has specific numbers, active voice, and no buzzwords.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ai-adoption-playbook:board-ai-updateThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Template for the AI section of a board update. Takes results data and produces a tight, number-filled narrative. This is the template — `board-narrative-coach` is the skill that rehearses and pressure-tests before drafting.
Template for the AI section of a board update. Takes results data and produces a tight, number-filled narrative. This is the template — board-narrative-coach is the skill that rehearses and pressure-tests before drafting.
Core principle: Every paragraph has a number. No number, no paragraph.
Produce the board update in this exact format:
## Board AI Update — [Quarter/Date]
**Company:** [name]
### What We Did
[1 paragraph. What was the initiative, who participated, what timeframe.
Must include: number of engineers, the specific use case, the duration.]
### What Happened
[1 paragraph. Results with specific numbers.
Must include: adoption rate, hours saved or cost avoided, quality signal, tool cost.
ROI calculation if the numbers support it.]
### What's Next
[1 paragraph. Forward-looking plan.
Must include: next use case, timeline, named owner, target metric for next quarter.]
For skeptical boards, add:
### Risks and Honest Assessment
[2-3 sentences. What's not working yet, what you're watching.
Shows self-awareness. Boards trust founders who name their own risks.]
Adapt to what the board expects:
| Board preference | Adjustment |
|---|---|
| Data-heavy | Add a metrics table between "What Happened" and "What's Next" |
| Narrative | Keep as-is, one paragraph per section |
| Slides | Convert each section to a slide title + 3-4 bullet points |
| Brief mention | Compress to 2-3 sentences total, lead with the strongest number |
Symptom: "We are leveraging AI to transform our development workflow and drive innovation across the organization." Consequence: Board learns nothing. Founder sounds like they're reading a press release. Fix: Replace with specifics. "8 engineers used AI code review for 2 months. 6 kept using it. They save about 6 hours per week combined. Tool costs $800/month."
Symptom: Update is mostly about what didn't work, framed defensively. Consequence: Board loses confidence. Founder sounds uncertain. Fix: Lead with what you did and what happened. Put risks in their own section, framed as self-awareness, not failure.
Symptom: "Saved 24 hours per month" with no reference point. Consequence: Board can't evaluate if that's good or bad. Fix: Always provide context. "24 hours/month across 6 engineers — about 4 hours each, or 30 minutes per day. Tool costs $800/month, which is $33 per hour of capacity recovered."
board-narrative-coach — rehearses the founder with hard questions before drafting; uses this template for the final outputroi-calculator — provides the numbers for the "What Happened" sectionadoption-scorecard — provides the adoption datanpx claudepluginhub adimango/ai-adoption-playbookRoleplays skeptical board member to stress-test founder's AI adoption progress, then drafts defensible board update narrative. For pre-board meeting prep.
Transforms raw product notes into structured executive briefings with headline, metrics, risks, decisions, and next steps. Useful for weekly updates or leadership syncs.
Generates structured monthly/quarterly investor updates with metrics table, highlights, challenges, next focus, and actionable asks. For startup progress reports or board newsletters.