Files
pm-claude-skills/plugins/pm-strategy/skills/executive-update/SKILL.md
T
mohitagw15856 513e1d3ce7 fix: sync all skill updates and new skills into plugin bundles
- Synced 97 existing skill SKILL.md files from skills/ to their plugin bundle copies
- Added 7 new skills to plugin bundles:
  - seo-content-brief, media-pitch -> pm-gtm
  - tax-planning-checklist -> pm-finance
  - change-management-plan -> pm-hr
  - sales-forecasting-model -> pm-sales
  - workshop-facilitation-guide -> pm-operations
  - teaching-lesson-plan -> pm-cross

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-04-20 21:00:08 +01:00

2.5 KiB

name, description
name description
executive-update Transform detailed product updates into concise executive briefings. Use when asked to write an executive update, leadership update, product update for the exec team, or a C-suite product briefing. Produces a structured 250-word briefing with headline, key metrics, progress, risks, decisions needed, and next steps.

Executive Update Skill

Produce a stakeholder update that busy executives will actually read — structured around what they care about: decisions, risks, and numbers.

Required Inputs

Ask the user for these if not provided:

  • Product update or notes (raw input to transform — even bullet points work)
  • Audience (CEO, board, specific exec, or general leadership)
  • Period (this week / sprint / month / quarter)
  • Key metrics (what numbers matter to this audience)

Executive Communication Principles

  • Lead with the headline, not the context
  • Every update should answer: "So what does this mean for the business?"
  • Flag decisions needed clearly — don't bury asks in paragraphs
  • Be honest about risks — executives hate surprises more than bad news

Process

  1. Read the full product update provided
  2. Identify: key metric movements, decisions required, risks to flag, wins to celebrate
  3. Write in reverse pyramid style — most important first
  4. Limit to 250 words maximum for the main body
  5. Add a "Decisions Needed" section with clear options and your recommendation
  6. Validate — Confirm every decision needed has a specific option and recommendation (not just "TBD"), and every risk has a mitigation or watch plan

Output Structure

Product Update — [Date / Sprint / Month]

Headline: [One sentence on the most important thing]

By the Numbers:

Progress This Period: [3-4 bullet points, outcome-focused not activity-focused]

Risks & Watch Items: [2-3 bullets — be direct, include mitigation]

Decisions Needed:

  1. [Decision] — Options: [A] or [B] — Recommendation: [your view] — Needed by: [date]

What's Next: [2-3 bullets on next period priorities]

Quality Checks

  • Whole update is under 250 words (if not, cut ruthlessly)
  • Every metric includes a comparison point (vs. target or last period)
  • Every risk has a mitigation or watch action
  • Every decision needed has at least two options and a recommendation
  • Written for a CFO or CEO — no jargon, all outcomes