exec-summary
Skill1 starsChanged 5 months agoMITView on GitHub
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.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- itgenius-au/skills-librarytheir own version, first seen Nov 1, 2026
- Lwhieldon/claude-project-mgmt-playbooktheir own version, first seen Oct 13, 2026
- teachskillofskills-ai/DigitalMarketingPro-techshutheir own version, first seen Oct 11, 2026
- modeled-information-format/mif-docs-plugintheir own version, first seen Oct 8, 2026
- Jiplet/transformation-ostheir own version, first seen Jul 2, 2026
- hamzafarooq/claude-code-startertheir own version, first seen May 8, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- indranilbanerjee/digital-marketing-pro★ 934same name
- hamzafarooq/claude-code-starter★ 145same name
- Lwhieldon/claude-project-mgmt-playbook★ 4same name
- Jiplet/transformation-os★ 2same name
- itgenius-au/skills-library★ 1same name
- modeled-information-format/mif-docs-plugin★ 1same name
- teachskillofskills-ai/DigitalMarketingPro-techshu★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository18 other files it gives its agents.
- capacity-planningSkill
- decision-logSkill
- dependency-mappingSkill
- escalationSkill
- estimation-sizingSkill
- launch-readinessSkill
- okr-trackingSkill
- postmortemSkill
- prd-reviewSkill
- program-health-dashboardSkill
- project-charterSkill
- raid-logSkill
- release-notesSkill
- retrospectiveSkill
- roadmap-planningSkill
- sprint-planningSkill
- stakeholder-comms-planSkill
- status-reportSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
One screen: If they want detail, they'll ask or click the appendix link.
- Distinctive: line 22
Write a headline (1 sentence): overall status + the thing that matters most.
- Distinctive: line 26
Add a one-line what's next and where to find detail.
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

