---
name: exec-briefing-writer
description: Turn a technical topic into an executive briefing — one page, one meeting, or one slide — with the business framing, decisions required, risks, and a specific ask, all in plain English.
version: 1.0.0
author: VantagePoint Networks
author_url: https://www.vpnetworks.co.uk
audience: IT Managers, CISOs, Platform Engineers, MSP Account Managers briefing client execs, anyone presenting tech to non-technical leadership
output_format: Formatted Markdown pack with three briefing variants (one-page memo, meeting-slot pack, single-slide deck), plus a speaking-notes track and anticipated Q&A.
license: MIT
last-reviewed: 2026-04
---

# Exec Briefing Writer

A Claude Code skill for turning a technical topic into something the Board, the Managing Partner, or the CEO can absorb in the time they have — one page, twenty minutes, or one slide — without losing the substance.

## How to use this skill

1. Download this `SKILL.md` file.
2. Place it in `~/.claude/commands/` (macOS/Linux) or `%USERPROFILE%\.claude\commands\` (Windows).
3. In Claude Code, run `/exec-briefing-writer`. Describe the topic and the audience. Answer the clarifying questions. Receive three briefing variants.

## When to use this

- You've been given "5 minutes at the partners' meeting on Thursday" to explain a technical initiative.
- A Board paper is due on a technology decision and the last one you wrote was too long.
- A client's exec has asked for an explanation of a proposed change and you need to match their vocabulary.
- You're proposing budget / headcount / a significant change and need to make the ask cleanly.
- Technical content has been lost in translation — executives approved but don't understand.

## What you'll get

A single Markdown document containing:

- **One-page memo** (600-800 words max; the full case)
- **Meeting-slot pack** (10 / 20 / 30-minute variants with spoken script)
- **Single-slide deck** (one slide, five content blocks, used as pre-read or in-meeting anchor)
- **Elevator version** (30 seconds, for corridor or follow-up)
- **Anticipated questions + answers** (8-12)
- **What to have at hand** (supporting detail ready if asked)

## Clarifying questions I will ask you

1. **What's the topic?** (one sentence)
2. **Who's the audience?** (Board, Partners, CEO, client exec, non-technical senior)
3. **What decision do you need from them?** (or: inform only)
4. **What's the ask — budget, people, sign-off, time, consent?**
5. **What's the time you have?** (1-page pre-read, 5-min slot, 20-min meeting, one slide)
6. **What do they know about this already?** (nothing / some / previously briefed)
7. **What's their biggest likely concern?** (cost, risk, disruption, precedent, regulator)
8. **What's the worst-case they'd ask "why didn't we do this sooner?"**
9. **Any recent context?** (incident, competitor move, regulator letter, client request)
10. **Can you use numbers?** (sensitive / yes / estimates only)
11. **Tone?** (measured / urgent / cautious / confident)
12. **Deadline?** (when's the meeting / when's it due)

## Output template

```markdown
# Exec Briefing — <topic> — <for whom> — <date>

## 1. One-Page Memo (600-800 words)

### <Topic> — briefing for <audience>
**Date:** <date> · **Author:** <role> · **Classification:** <internal / board>

**The ask (one sentence):** <e.g. "Approve £60k budget over 6 months to implement Cyber Essentials Plus and consolidate backup tooling.">

**Why now:**
<2-3 sentences. What's changed that makes this a decision today rather than next year.>

**What we're proposing:**
<2-3 sentences. The change, in business-language. Avoid jargon. If a technical term is unavoidable, define it once in brackets.>

**Why this approach (vs alternatives considered):**
<short paragraph. State the options considered and why this one wins on the criteria that matter to THIS audience (cost / risk / speed / regulatory fit).>

**Impact if approved:**
- <benefit 1 — specific, measurable where possible>
- <benefit 2>
- <benefit 3>

**Impact if we don't act:**
- <consequence 1>
- <consequence 2>

**Cost & resources:**
- £<N> one-off, £<N>/year ongoing
- <N> FTE hours from <teams>
- Timeline: <start> to <milestone>

**Risks:**
- <risk 1> — <mitigation>
- <risk 2> — <mitigation>

**Decision requested:**
<specific, yes/no or options>.

**Decision by:** <date>.

## 2. Meeting-Slot Pack

### 5-minute slot (lightning)
| Minute | Content |
|---|---|
| 0:00-0:30 | Opening: "Five minutes on <topic>. I'm asking for <decision>." |
| 0:30-2:00 | Why now: one story or one data point that makes the timing real. |
| 2:00-3:30 | What we're proposing + what it costs. |
| 3:30-4:30 | What happens if we don't act. |
| 4:30-5:00 | "I need a decision by <date>. Happy to take questions now or follow up." |

### 20-minute slot
| Minute | Content |
|---|---|
| 0-2 | Opening + ask |
| 2-5 | The problem / opportunity |
| 5-9 | Proposed approach, alternatives considered |
| 9-13 | Cost, timeline, resources |
| 13-16 | Risks + mitigations |
| 16-18 | What success looks like + how we'll measure |
| 18-20 | Close + decision request |

## 3. Single-Slide Deck
Title: **<Topic> — decision requested**

| Block | Content |
|---|---|
| **Why now** | <1 line> |
| **Proposal** | <1 line> |
| **Cost** | £<N> one-off, £<N>/yr. Time: <N> months. |
| **Benefits** | • <> • <> • <> |
| **Risks** | • <risk + mitigation> • <> |

Footer: **Decision by <date>. Ask: <specific>.**

## 4. Elevator Version (30 seconds)
> "<30-second version. Problem, proposal, cost, decision needed, when.>"

Example:
> "We've drifted into a state where no third-party tool backs up our M365. Microsoft's own retention won't recover us from a malicious deletion. Veeam M365 Essentials costs £2,500 a year. I'd like sign-off to buy it this week and roll out by end of month. It closes the biggest single gap in our cyber posture."

## 5. Anticipated Questions & Answers
1. **"Why didn't we do this sooner?"** — <specific, honest answer that doesn't throw anyone under the bus>
2. **"How much is it really going to cost?"** — <the full cost, not the headline>
3. **"What happens if we do nothing?"** — <honest downside, quantified if possible>
4. **"Who else is doing this?"** — <peer comparison or market context>
5. **"Can we do it cheaper?"** — <the cheaper option and why you didn't choose it>
6. **"Is this reversible if it doesn't work?"** — <yes / no / partially>
7. **"Who owns it after approval?"** — <named role>
8. **"What's the first milestone we'll see?"** — <specific, near-term>
9. **"What are we NOT doing because we're doing this?"** — <honest trade-off>
10. **"What if the regulator/client asks about it?"** — <positioning>
11. **"Can we pilot this before committing?"** — <yes, here's how / no, here's why>
12. **"What's the worst-case scenario?"** — <realistic worst case, not doom>

## 6. What to Have at Hand (if asked)
- Supporting cost analysis (detailed breakdown)
- Vendor shortlist with selection criteria
- Risk register
- Timeline / Gantt
- Reference deployments / case studies
- Alternative options with fuller trade-off analysis
- Relevant regulator / contract clauses

## 7. Tone Guidance
For the specified audience (<audience type>):
- Use <business / technical / mixed> vocabulary.
- Lead with <risk / opportunity / compliance>.
- Keep graphs / slides / numbers <minimal / moderate / detailed>.
- Expect interruptions: <few / frequent>.
- Decision style: <consensus / decisive single / structured deliberation>.
```

## Example invocation

**User:** "I need to brief the Managing Partners on introducing Microsoft Copilot for all fee-earners. Got 10 minutes at Tuesday's partners meeting. Budget ask is £24k/year. Partners are split: some keen, some deeply sceptical about AI and client confidentiality."

**What the skill will do:**
1. Ask 12 questions, pressing on: what specifically concerns the sceptical partners (SRA privilege? training on client data? hallucination?), who the most influential sceptic is, whether any peer firms are already using Copilot.
2. Produce the three variants:
   - 800-word memo framing Copilot as "sovereignty-preserving AI with EU Data Boundary" — language that resonates with legal professionals
   - 10-minute script with 2 minutes specifically addressing the sceptic case (privilege, data boundary, opt-out options, supervised rollout)
   - Single slide with the decision and a specific 90-day pilot proposal
3. Anticipated Q&A tailored to partner-meeting dynamics: "What if a junior pastes privileged material by mistake?" — with the honest, specific answer.
4. Flag that offering a 10-seat pilot first (not a full rollout) is usually the right framing for split partnerships.

## Notes for the requester

- **Write for the person who doesn't already agree with you.** Your strongest sceptic is the reader you're drafting for.
- **The ask comes first, not last.** Tell them what you need in the opening sentence. Save nuance for paragraph 3.
- **Numbers you don't know: estimate and say so.** "£24k ± 10%" is better than "roughly £20-30k" and infinitely better than "it depends."
- **Anticipate "why didn't we do this sooner?"** — it's the most common question, and the one that derails briefings when unprepared.
- **Write the elevator version last, share it first.** If a partner gets the elevator, they can ask for the one-page. If they get the one-page first, they may not read it.
- **Good looks like:** a decision is made in the scheduled time, the approver can articulate WHY in one sentence afterwards, and the follow-up action list is specific.

---
*VantagePoint Networks · <https://www.vpnetworks.co.uk> · Authored by Hak · Free under the MIT licence*