hardiktiwari/PM-operating-OS / skills/exec-communicator
exec-communicator
VerifiedHelp PMs write clear, executive-ready communications. Use for status updates, escalations, decision requests, launch announcements, or leadership briefings.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 2.5 KB |
SKILL.md
View on GitHub---
name: exec-communicator
description: "Help PMs write clear, executive-ready communications. Use for status updates, escalations, decision requests, launch announcements, or leadership briefings."
---
# Exec Communicator
Help PMs write clear, executive-ready communications using BLUF (Bottom Line Up Front) format. Produces scannable, decision-oriented content for leadership and stakeholders.
## When to Use
- Writing weekly or bi-weekly status updates
- Escalating a risk or blocker to leadership
- Requesting a decision from stakeholders
- Drafting internal launch announcements for executives
- Preparing quarterly business review input
- When asked "help me write this for leadership"
## Process / Template
### 1. Identify Communication Type
Ask: What type of communication is needed?
- **Status update** — progress vs. plan, metrics, risks
- **Escalation** — issue, impact, options, recommendation
- **Decision request** — context, options, trade-offs, deadline
- **Launch announcement** — what shipped, who it's for, impact
### 2. Gather Key Inputs
- What happened? (facts, metrics, outcomes)
- What's at risk? (blockers, dependencies)
- What do you need? (decision, resources, air cover)
- When is the deadline?
### 3. Apply BLUF Principles
- **Lead with the "so what"** — one sentence summary first
- **Be specific** — numbers, dates, named stakeholders
- **Tie to metrics and strategy** — connect to goals and OKRs
- **Anticipate questions** — address likely objections proactively
- **Keep it scannable** — bullets over paragraphs, headers for sections
### 4. Use the Right Template
**Status Update:**
- **TL;DR** — one sentence summary
- **Progress vs. Plan** — on track / at risk / behind
- **Key Metrics** — numbers that matter
- **Risks/Blockers** — what could derail
- **Asks** — what you need from leadership
**Escalation:**
- **Issue** — what's wrong (1–2 sentences)
- **Impact** — quantified (revenue, timeline, customers)
- **Options** — 2–3 paths forward with pros/cons
- **Recommendation** — what you recommend and why
- **Timeline** — when a decision is needed
**Decision Request:**
- **Context** — 2 sentences max
- **Decision Needed** — explicit ask
- **Options with Trade-offs** — pros/cons per option
- **Recommendation** — your call
- **Deadline** — when to decide
## Output
A polished, executive-ready communication in the requested format. Scannable, specific, and action-oriented. Ready to paste into email, Slack, or a deck.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |