exec-summary

Name: exec-summary
Author: Productfculty-aipm

70stars33forks

How to install exec-summary?

productfculty-aipm/pm-copilot-by-product-faculty/exec-summary

$npx -y skills add Productfculty-aipm/PM-Copilot-by-Product-Faculty --skill exec-summary

Installs into the current project.

Summary

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 initia

Files · 1

View on GitHub

SKILL.md

1	# Executive Summary
2
3	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.
4
5	Framework: Pyramid Principle (Barbara Minto), SCR framework (Situation / Complication / Resolution), Lenny's 14 PM habits (clarity is the most fundamental PM skill).
6
7	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)
8
9	## Step 1 — Load Context
10
11	Read `memory/user-profile.md` for: stakeholder context (who is this going to, their communication style and sensitivities), product context, and current initiative status.
12
13	## Step 2 — Identify the Point
14
15	Before writing, answer: what is the single most important thing the reader needs to know or do?
16
17	This is the "bottom line up front" — the executive summary's headline. It should be:
18	- A conclusion, not a status update: "We need to delay launch by 2 weeks" not "Launch preparation is ongoing"
19	- An action or decision request, if one is needed: "I recommend we proceed with Option B"
20	- A risk or signal, if nothing else: "We have early indicators that the North Star metric is moving"
21
22	If the user can't articulate the bottom line in one sentence, help them find it before writing.
23
24	## Step 3 — SCR Structure
25
26	Structure the executive summary using Situation / Complication / Resolution:
27
28	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."
29
30	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."
31
32	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]."
33
34	## Step 4 — Executive Summary Format
35
36	Depending on the context, format as:
37	- Slack message: 3–5 sentences using SCR implicitly. No headers. Bottom line first.
38	- Email: Subject line = the bottom line. Body = SCR in 3 short paragraphs. Max 200 words.
39	- Slide: One headline = the insight. 3 supporting bullets. One action item.
40	- Verbal briefing (script): 90 seconds. Open with bottom line. 2–3 supporting facts. Close with what you need from them.
41
42	Ask the user which format they need if it's not obvious.
43
44	## Step 5 — Exec-Calibrated Language
45
46	Apply these rules for executive communication:
47	- Use numbers when you have them: "7-day retention dropped 4 points" beats "retention is declining"
48	- Acknowledge uncertainty explicitly: "We believe X, but won't know for certain until [date]"
49	- Never bury the ask: the decision or action needed should be in the first or last sentence, not the middle
50	- One risk, not a list: executives worry about lists of risks — they want the one thing that matters most
51	- No jargon from internal tools: say "the team's tracking system" not "Linear"
52
53	## Step 6 — Output
54
55	Produce:
56	- The executive summary in the requested format
57	- An alternative if the user might need both Slack and email versions
58	- Flagged risks: any element of the summary that might push back from this specific stakeholder (based on their sensitivities in memory)

Productfculty-aipmPublisher · 69 listings

Preview

Productfculty-aipm/PM-Copilot-by-Product-Faculty

# Executive Summary

You are writing an executive summary using the Pyramid Principle — the communication framework used by McKinsey and the most effective PM communicators. The key

Framework: Pyramid Principle (Barbara Minto), SCR framework (Situation / Complication / Resolution), Lenny's 14 PM habits (clarity is the most fundamental PM sk

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 Manage

RepoProductfculty-aipm/PM-Copilot-by-Product-Faculty

License—

TypeSkills

CategoryDocumentation

UpdatedApr 2026

Repo stars70

First seenJul 22, 2026

People who liked this also viewed

6 picks

Type

exec-summary

70stars33forks

View on GitHub

How to install exec-summary?

productfculty-aipm/pm-copilot-by-product-faculty/exec-summary

$npx -y skills add Productfculty-aipm/PM-Copilot-by-Product-Faculty --skill exec-summary

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Executive Summary
2
3	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.
4
5	Framework: Pyramid Principle (Barbara Minto), SCR framework (Situation / Complication / Resolution), Lenny's 14 PM habits (clarity is the most fundamental PM skill).
6
7	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)
8
9	## Step 1 — Load Context
10
11	Read `memory/user-profile.md` for: stakeholder context (who is this going to, their communication style and sensitivities), product context, and current initiative status.
12
13	## Step 2 — Identify the Point
14
15	Before writing, answer: what is the single most important thing the reader needs to know or do?
16
17	This is the "bottom line up front" — the executive summary's headline. It should be:
18	- A conclusion, not a status update: "We need to delay launch by 2 weeks" not "Launch preparation is ongoing"
19	- An action or decision request, if one is needed: "I recommend we proceed with Option B"
20	- A risk or signal, if nothing else: "We have early indicators that the North Star metric is moving"
21
22	If the user can't articulate the bottom line in one sentence, help them find it before writing.
23
24	## Step 3 — SCR Structure
25
26	Structure the executive summary using Situation / Complication / Resolution:
27
28	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."
29
30	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."
31
32	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]."
33
34	## Step 4 — Executive Summary Format
35
36	Depending on the context, format as:
37	- Slack message: 3–5 sentences using SCR implicitly. No headers. Bottom line first.
38	- Email: Subject line = the bottom line. Body = SCR in 3 short paragraphs. Max 200 words.
39	- Slide: One headline = the insight. 3 supporting bullets. One action item.
40	- Verbal briefing (script): 90 seconds. Open with bottom line. 2–3 supporting facts. Close with what you need from them.
41
42	Ask the user which format they need if it's not obvious.
43
44	## Step 5 — Exec-Calibrated Language
45
46	Apply these rules for executive communication:
47	- Use numbers when you have them: "7-day retention dropped 4 points" beats "retention is declining"
48	- Acknowledge uncertainty explicitly: "We believe X, but won't know for certain until [date]"
49	- Never bury the ask: the decision or action needed should be in the first or last sentence, not the middle
50	- One risk, not a list: executives worry about lists of risks — they want the one thing that matters most
51	- No jargon from internal tools: say "the team's tracking system" not "Linear"
52
53	## Step 6 — Output
54
55	Produce:
56	- The executive summary in the requested format
57	- An alternative if the user might need both Slack and email versions
58	- Flagged risks: any element of the summary that might push back from this specific stakeholder (based on their sensitivities in memory)

Productfculty-aipmPublisher · 69 listings

Preview

Productfculty-aipm/PM-Copilot-by-Product-Faculty

# Executive Summary

You are writing an executive summary using the Pyramid Principle — the communication framework used by McKinsey and the most effective PM communicators. The key

Framework: Pyramid Principle (Barbara Minto), SCR framework (Situation / Complication / Resolution), Lenny's 14 PM habits (clarity is the most fundamental PM sk

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 Manage

RepoProductfculty-aipm/PM-Copilot-by-Product-Faculty

License—

TypeSkills

CategoryDocumentation

UpdatedApr 2026

Repo stars70

First seenJul 22, 2026

People who liked this also viewed

6 picks

Type