Brief executives with the answer first, the whole thing on one page, risks paired with the decision you need, and no surprises. Use when you must get a decision or an update in front of leadership who have five minutes and no context.
Scanned 9/5/2026
Install to Claude Code
npx -y skills add Amey-Thakur/AI-SKILLS --skill exec-briefing --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Exec Briefing?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/amey-thakur-exec-briefing)More formats (shields.io, HTML) on the badges page.
---
name: exec-briefing
description: Brief executives with the answer first, the whole thing on one page, risks paired with the decision you need, and no surprises. Use when you must get a decision or an update in front of leadership who have five minutes and no context.
---
# Executive briefing
An executive reads your brief between two other meetings and needs the decision,
not the journey. The common failure is a slow build: background, then analysis,
then finally the ask on page four, by which point the reader has skimmed to the
end looking for it anyway. Lead with the conclusion and earn the rest of their
attention with it.
## Method
1. **Open with the answer, in the first two sentences.** State the
recommendation or the status, then the one number that proves it.
"We should delay the launch two weeks; the payments path fails
one in twenty test transactions." Everything after this exists to
support a conclusion the reader already has.
2. **Fit it on one page.** If it does not fit, you have not decided what matters
yet. One page forces the ruthless cut between what the executive needs and
what you are proud of having found. Detail goes in an appendix they can open
if they choose to.
3. **Pair every risk with an ask.** A risk without a request is a worry you
handed upward; a risk with a request is a decision you enabled. "Vendor may
miss the date (risk); approve the backup contract by Friday (ask)."
Executives exist to unblock, so give them the specific lever to pull.
4. **Kill the surprises before the meeting.** Pre-brief anyone who would be
blindsided or would object in the room: your skip-level, the affected peer,
finance. A briefing is where a decision is ratified, not where a fight
starts. If someone will push back hard, they should have already pushed
back in private.
5. **Quantify, and show the range.** Replace "significant delay" with "three to
five weeks, most likely four." Executives calibrate on numbers and distrust
adjectives. When you are uncertain, state the range and the assumption
driving it rather than hiding behind a soft word.
6. **End with what you need and by when.** Close on the decision, the owner, and
the date. "Need go/no-go on the migration by end of week to hold the Q3
date." A brief that trails off into "happy to discuss" wasted the one chance
to get a commitment.
## Litmus tests
- If the reader stopped after the first paragraph, would they have the decision?
- Does every risk name the specific action you want taken about it?
- Is there anyone who would be surprised in the room, and have you pre-briefed
them?
## Boundaries
This is the format for a decision or status brief, not a strategy narrative that
argues a case over several pages: for that reach for the six-pager-narrative
skill. Norms on length and pre-read culture vary by company and by executive;
learn what your specific audience reads and rewards.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!