Help us improve
Share bugs, ideas, or general feedback.
From pm-copilot
Use this skill when the user asks to "write an exec summary", "summarize this for leadership", "write a summary for the CEO", "board update summary", "executive brief", "leadership update", "write this for C-level", or needs to communicate a complex situation, decision, or initiative status to senior leadership in a concise, structured format. Do NOT use this skill for full stakeholder updates with multiple audience versions — use stakeholder/audience-tailoring for that.
npx claudepluginhub productfculty-aipm/pm-copilot-by-product-facultyHow this skill is triggered — by the user, by Claude, or both
Slash command
/pm-copilot:exec-summaryThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are writing an executive summary using the Pyramid Principle — the communication framework used by McKinsey and the most effective PM communicators. The key principle: lead with the conclusion, not the journey to reach it.
Transforms detailed product updates into concise executive briefings with headline, key metrics, risks, decisions, and next steps.
Produces one-page executive summaries, briefs, and board-level documents by extracting situation, key findings, implications, and a clear recommendation for senior decision-makers.
Transforms raw notes into polished stakeholder updates for email, Slack, or deck bullets. Structures TL;DR, progress, blockers, decisions needed, and next priorities. Ideal for crisp status reports.
Share bugs, ideas, or general feedback.
You are writing an executive summary using the Pyramid Principle — the communication framework used by McKinsey and the most effective PM communicators. The key principle: lead with the conclusion, not the journey to reach it.
Framework: Pyramid Principle (Barbara Minto), SCR framework (Situation / Complication / Resolution), Lenny's 14 PM habits (clarity is the most fundamental PM skill).
Key principle from Lenny: "Great PMs take pride in clarity. They never make the listener work to find the point." — 14 Habits of Highly Effective Product Managers, Lenny Rachitsky (2021)
Read memory/user-profile.md for: stakeholder context (who is this going to, their communication style and sensitivities), product context, and current initiative status.
Before writing, answer: what is the single most important thing the reader needs to know or do?
This is the "bottom line up front" — the executive summary's headline. It should be:
If the user can't articulate the bottom line in one sentence, help them find it before writing.
Structure the executive summary using Situation / Complication / Resolution:
Situation (1–2 sentences): The context the reader needs to understand. What's the current state? Assume the reader knows the basics and skip the background. Situation = "Here's where we are."
Complication (1–3 sentences): What's changed, at risk, or needs a decision. This is the tension that requires the reader's attention. Complication = "But here's the problem / challenge / opportunity."
Resolution (2–4 sentences): What you recommend, what you've decided, or what you need from the reader. This should be specific — not "we're monitoring the situation" but "I recommend X because Y. I need Z from you by [date]."
Depending on the context, format as:
Ask the user which format they need if it's not obvious.
Apply these rules for executive communication:
Produce: