Skill

Skill: executive-summary

Generate a concise, one-page executive summary of delivery health — suitable for C-suite, board updates, or steering committee packets.

Install

npx claudepluginhub devmuslim/pdm-skills --plugin pdm-stakeholder-delivery

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Generate a concise, one-page executive summary of delivery health — suitable for C-suite, board updates, or steering committee packets.

SKILL.md

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

139.0k

claude-opus-4-5-migration

2 files

Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.

claude-opus-4-5-migration

83.2k

bmad-editorial-review-prose

Reviews prose for communication issues impeding comprehension, outputs minimal fixes in a three-column table per Microsoft Writing Style Guide. Useful for 'review prose' or 'improve prose' requests.

bmad-pro-skills

43.8k

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitMar 9, 2026

Actions

View Source View Plugin View on GitHub View README

Skill: executive-summary

Purpose

Generate a concise, one-page executive summary of delivery health — suitable for C-suite, board updates, or steering committee packets.

When to Use

Monthly business review
Steering committee preparation
When a senior leader asks "how are we doing?"

Framework: Executive Delivery Summary

Principle

Executives need signal, not noise. Every sentence must earn its place. Format: What, So What, Now What.

Step 1 — Gather Inputs

Ask for:

Release or programme name
Target date and current forecast
Budget status (if relevant)
Top 1–2 risks
Any decisions needed from leadership

Step 2 — One-Page Summary Format

[Release / Programme Name] — Delivery Summary As of [Date] | Prepared by [Name]

Overall Status: 🟢 On Track / 🟡 At Risk / 🔴 Off Track

	Planned	Forecast	Variance
Release Date	[date]	[date]	[+/- days]
Scope	100%	[X]%	[-Y items deferred]
Budget	$X	$Y	[+/- Z%]

Progress This Period

[2–3 bullet points: what was completed]

Risks & Issues

Risk/Issue	Impact	Action	Owner
[Top risk]	High	[Mitigation]	[Name]

Decisions Needed

[Explicit ask 1 — by when]
[Explicit ask 2 — by when]

Next Milestone [Milestone name] — [Date] — [Owner]

Step 3 — Tone Rules for Executive Writing

Lead with status (don't bury it)
Use numbers, not adjectives ("3 weeks late" not "significantly delayed")
Name owners explicitly
Make asks specific ("Approve budget increase of $50K by Friday")
No jargon (no "sprint velocity", "P1 bugs", "CI/CD")

Output Format

Completed one-page executive summary
Talking points for verbal delivery (3 bullets)
Suggested next command: /steering-deck or /status-update