mcpField
E
executive-briefs

executive-briefs

github.com/gtmagentsDocuments42872 installsUpdated 30w ago
Repository

About executive-briefs

An executive-briefing skill for shaping forecast updates into decision-oriented memos and presentations for ELT or board audiences. It combines audience-aware framing, evidence, clear requests, and an audit trail.

Key features

  1. 01Audience-focused framing
  2. 02Headline, drivers, and mitigation plan
  3. 03Charts, tables, and footnotes
  4. 04Explicit decisions and requests
  5. 05Appendix links and audit trail
  6. 06Summary, memo, and risk templates

Use cases

  1. 01Preparing a board forecast update
  2. 02Explaining revenue risks and opportunities
  3. 03Turning forecast and variance analysis into meeting materials

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/gtmagents/gtm-agents --skill executive-briefs

After installing, type/executive-briefsin Claude Code to confirm it loaded.

Details

From the project README

Executive Brief System Skill

When to Use

  • Delivering forecast updates to ELT or board audiences.
  • Summarizing revenue risks/opportunities with clear asks.
  • Packaging meeting-ready decks or memos that pull from forecast + variance analysis outputs.

Framework

  1. Audience Lens – capture what the audience cares about (growth, margin, cash, runway) and tailor tone.
  2. Story Arc – set context, state the headline (ahead/behind), outline drivers, and present mitigation plan.
  3. Evidence Layer – include key charts/tables with consistent formatting + footnotes.
  4. Decision & Ask – specify what approval, resource shift, or unblock is needed.
  5. Appendix & Audit Trail – link to deeper dashboards, logs, and forecast files for transparency.

Templates

  • One-slide executive summary (headline, numbers, drivers, actions).
  • Board memo outline (context, highlights, lowlights, requests).
  • Risk register snippet for ongoing tracking.

Tips

  • Use consistent metric definitions and color-coding to avoid confusion.
  • Keep main section under one page/slide, move detail to appendix.
  • Reference variance-analysis findings and forecast-modeling assumptions in footnotes.

Comments

Markdown supported