playbooks

home / skills / gtmagents / gtm-agents / exec-briefing

exec-briefing skill

/plugins/account-management/skills/exec-briefing

This skill helps craft concise executive updates and meeting follow-ups for QBR/EBR, aligning outcomes, risks, and actions across stakeholders.

npx playbooks add skill gtmagents/gtm-agents --skill exec-briefing

Review the files below or copy the command above to add this skill to your agents.

Files (2)
SKILL.md
1.3 KB
---
name: exec-briefing
description: Use to craft concise executive updates, agendas, and follow-up logs for
  QBR/EBR sessions.
---

# Executive Briefing Kit Skill

## When to Use
- Preparing QBR/EBR agendas that include executive stakeholders.
- Summarizing account impact stories for CRO/CEO/CTO readouts.
- Documenting commitments and follow-ups after executive meetings.

## Framework
1. **Audience Lens** – capture what each executive cares about (business outcomes, risk, roadmap, financial impact).
2. **Narrative Structure** – headline, metrics, proof, decisions/asks, next steps.
3. **Visual Layer** – standardized slides/one-pagers with consistent KPIs and color coding.
4. **Decision Log** – track approvals, risks, and owners for follow-ups.
5. **Distribution Plan** – define recipients, timing, and archival location.

## Templates
- **Briefing Doc**: See `templates/briefing_doc.md` for agenda and summary structure.
- **Executive summary slide** (headline, impact, next action).
- **Meeting brief** (objectives, attendees, agenda, prep requirements).
- Decision log table with owners and deadlines.

## Tips
- Keep top section under 150 words; move detail to appendix.
- Pair with `success-planning-framework` to ensure talking points align to milestones.
- Send recap within 24 hours to reinforce commitments.

---

Overview

This skill helps craft concise executive updates, agendas, and follow-up logs for QBR and EBR sessions. It standardizes headlines, metrics, decisions, and next steps so leadership gets the signal without the noise. Use it to align GTM teams and preserve a clear decision record for accountability.

How this skill works

The skill applies an audience lens to identify what each executive cares about (outcomes, risk, roadmap, financial impact). It builds a tight narrative—headline, key metrics, proof, decisions/asks, and next steps—and produces a briefing doc, one-slide summary, and a decision log. It also suggests distribution timing and archival location to ensure follow-through.

When to use it

  • Preparing QBR/EBR agendas involving C-suite or executive sponsors
  • Summarizing account impact stories for CRO, CEO, or CTO readouts
  • Documenting commitments, approvals, and owners after executive meetings
  • Creating a single-page executive summary for cross-functional reviews
  • Sending a concise recap within 24 hours to reinforce decisions

Best practices

  • Lead with a one-line headline that states the outcome or ask
  • Keep the top section under 150 words; move detail to an appendix
  • Include 3–5 KPIs that directly map to executive priorities
  • Use a decision log with owners, deadlines, and risk level for follow-up
  • Standardize slide visuals and color coding across briefings
  • Distribute to a defined recipient list and archive in a consistent location

Example use cases

  • Create a 3-slide QBR packet: headline slide, metrics slide, decisions and next steps
  • Draft an executive readout summarizing revenue impact and product risks
  • Produce a meeting brief with objectives, attendees, and prep requirements
  • Generate a post-meeting follow-up capturing decisions, owners, and deadlines
  • Turn a detailed account review into a one-page summary for the CEO

FAQ

How long should the executive summary be?

Keep the top-level summary under 150 words and use an appendix for supporting detail.

What belongs in the decision log?

Include the decision, rationale, owner, deadline, and risk level so follow-up is unambiguous.

When should I send the recap?

Send the recap within 24 hours to reinforce commitments and keep momentum.