Transform detailed product updates into concise executive briefings. Use when asked to write an executive update, leadership update, product update for the exec team, or a C-suite product briefing. Produces a structured 250-word briefing with headline, key metrics, progress, risks, decisions needed, and next steps.
▸Product update or notes — raw input to transform — even bullet points work
▸Audience — CEO, board, specific exec, or general leadership
▸Period — this week / sprint / month / quarter
▸Key metrics — what numbers matter to this audience
✅ The bar it holds itself to
Every skill in this library self-verifies — these are this skill's own quality checks, straight from its definition.
✓Whole update is under 250 words (if not, cut ruthlessly)
✓Every metric includes a comparison point (vs. target or last period)
✓Every risk has a mitigation or watch action
✓Every decision needed has at least two options and a recommendation
✓Written for a CFO or CEO — no jargon, all outcomes
⚠️ What it refuses to do
Do not lead with context or background — executives read the headline first; bury the important thing below two sentences of setup and they will miss it
Do not present metrics without a comparison point — a number without context (vs. target, vs. last period) cannot be interpreted and will prompt follow-up questions
Do not soften or spin risks — executives rely on these updates to make resource and escalation decisions; sanitised risk sections destroy the update's utility
Do not present a "Decisions Needed" item without a recommendation — asking an executive to decide without your view forces them to do the analytical work the PM should have done
Do not exceed 250 words in the main body — length signals the author has not done the compression work; every word over 250 reduces the chance the update is read
Install
npx pm-claude-skills add --agent claude # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y pm-claude-skills-mcp
Example output
Input: Audience: CEO. Period: Q2. Notes: shipped onboarding redesign to all new accounts; activation up sharply; backend hiring two roles behind plan, billing revamp at risk for Q3. Metrics: weekly active accounts, activation rate, NRR. · representative example (hand-written)