agentleFS
janelleciprianojanellecipriano/pm-skills/skills/exec-summary/SKILL.md

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

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
  1. Distinctive:

    One screen: If they want detail, they'll ask or click the appendix link.

    line 19
  2. Distinctive:

    Write a headline (1 sentence): overall status + the thing that matters most.

    line 22
  3. Distinctive:

    Add a one-line what's next and where to find detail.

    line 26

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Write a headline (1 sentence): overall status + the thing that matters most.
  2. Give status (🟢/🟡/🔴) with a one-line why.
  3. List 3–5 key points — progress, risks, changes — as outcomes with impact.
  4. State decisions/asks needed: each as a clear question with options and a recommendation.
  5. 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.