Exec summary
Open-source Claude skills for Program Management in product development — charters, status reports, RAID logs, roadmaps, launch readiness, retros, postmortems, OKRs & more.
npx -y skills add janellecipriano/pm-skills --skill exec-summaryAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Distill a detailed program update, document, or set of notes into a one-screen executive summary written for leadership — headline, status, key points, and decisions needed. Use when the user says "exec summary", "summarize for leadership", "TL;DR for the VP", "make this executive-ready", or needs to compress detail into a decision-focused brief.
SKILL.md
1.8 KB, as published. Nobody here has run it
Executive Summary
Compress detail into a brief a senior leader can absorb in 30 seconds and act on.
When to use
- Preparing an update for execs/leadership/steering committee.
- Turning a long doc, status, or thread into a leadership-ready summary.
Principles
- Lead with the answer. Headline first: status + the single most important thing.
- Decisions over description. Leaders read to decide — make asks explicit and easy to say yes/no to.
- Altitude. Outcomes and business impact, not implementation detail. Cut jargon.
- One screen. If they want detail, they'll ask or click the appendix link.
Process
- Write a headline (1 sentence): overall status + the thing that matters most.
- Give status (🟢/🟡/🔴) with a one-line why.
- List 3–5 key points — progress, risks, changes — as outcomes with impact.
- State decisions/asks needed: each as a clear question with options and a recommendation.
- Add a one-line what's next and where to find detail.
Output format
**{{Program}} — Executive Summary · {{date}}**
**Headline:** {{status + most important thing}}
**Status:** 🟢/🟡/🔴 — {{why}}
**Key points**
- {{outcome + impact}}
**Decisions needed**
- {{question}} — *recommend:* {{option}}. Needed by {{date}}.
**Next:** {{one line}} · Detail: {{link}}
Ruthlessly cut anything a VP wouldn't act on. Quantify where possible.