exec-briefing
/exec-briefing
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.
- Author
- Amey-Thakur ↗
- Repository
- AI-SKILLS ↗
- Licence
- MIT
- Last repository change
- 05.09.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 05.09.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
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.
Original author 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.
How it works
- Method
- Litmus tests
- Boundaries
SKILL.md preview
--- 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.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · Amey-Thakur/AI-SKILLS | 90 | MIT |
| criptogus/agent-evolve-network | 90 | Apache-2.0 |
Database snapshot: 13.11.2026 · package version b086026d0cf6 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100partner-exec-briefing
Prepares an executive for an exec-to-exec partner meeting with a one-page brief and a post-meeting capture template. Use when: exec briefing, executive meeting prep, exec-to-exec, partner CEO meeting, sponsor meeting, briefing doc, prep my VP for a partner call. - 90competitive-exec-brief
Creates an executive-ready competitive analysis brief with a 1-slide PPTX summary for leadership presentations. Use when: competitive brief, exec competitive summary, competitive slide, competitive pptx, board competitive update, leadership competitive briefing. - 100weekly-exec-brief
Use for this week's update for leadership, weekly executive brief, Monday briefing or Friday close. Load before drafting, even if records are missing or the request supplies wording. Summarise changes, commitments and decisions needed. Keep unsupported claims unverified. Use… - 100industry-briefing
Weekly executive intelligence briefing on the user's industry - the 10-15 most significant developments of the past 7 days ranked by business impact, their immediate / 6-12 month / long-term implications, what leadership teams are likely discussing, hiring and career… - 96om-exec-storyline
Write executive storylines, board memos and consulting-style decks: answer first (pyramid principle), situation–complication–question–answer, action titles that tell the story alone, one message per page, exhibits that prove the title, an executive summary and a decision page.… - 95decision-briefing
每当有多个决策挂起或积压时使用——无论是在特定主题、项目、文档中,还是在整个会话期间:对它们进行盘点,提供带有 A/B/C/D 选项及明确推荐的编号简报,接受字母答复(包括批量答复),记录结果并写回源文档。