# Stakeholder Update

> Help PMs write concise status updates for leadership and stakeholders. Use for weekly updates, milestone reports, or progress summaries.

- Skill: `sach1ng/stakeholder-update` (Agent Skill)
- Install (CLI): `npx skillmds@latest add sach1ng/stakeholder-update`
- Raw SKILL.md: https://api.skillmd.com/api/skills/sach1ng/stakeholder-update/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- Author: Sach1ng (https://skillmd.com/u/sach1ng)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/sach1ng/stakeholder-update

---


# Stakeholder Update

Help PMs write concise status updates for leadership and stakeholders. Produces scannable, metric-driven summaries that keep everyone informed without overwhelming.

## When to Use

- Weekly or bi-weekly status updates
- Milestone or phase completion reports
- Progress summaries for leadership
- Cross-team or cross-org updates
- When asked "send an update to [stakeholder]"

## Process / Template

### 1. Identify Audience and Cadence

- Who is the audience? (leadership, peers, cross-functional)
- How often? (weekly, bi-weekly, ad hoc)
- What do they care about? (metrics, risks, decisions)

### 2. Gather Content

- Progress since last update
- Key metrics (current vs. target)
- Wins and milestones
- Risks and blockers
- Decisions needed
- Next period focus

### 3. Structure the Update

**TL;DR**
- One sentence: on track / at risk / behind, plus headline

**Progress**
- 3–5 bullets: what shipped, what advanced, what's in progress
- Tie to goals or milestones where possible

**Metrics**
- Key numbers (current vs. target or prior period)
- Trend direction (↑ ↓ →)

**Risks / Blockers**
- What could derail
- What you need (decision, resource, escalation)

**Next Up**
- Top 2–3 priorities for the coming period

**Asks**
- Explicit: what you need from the reader

### 4. Apply Principles

- **Lead with the headline** — don't bury the lead
- **Be specific** — numbers, dates, names
- **Keep it scannable** — bullets, headers, white space
- **Anticipate questions** — address likely concerns
- **End with clarity** — what's next, what's needed

## Output

A **Stakeholder Update** that:
- Can be read in under 2 minutes
- Clearly signals status (green/yellow/red)
- Highlights metrics and progress
- Makes asks explicit
- Is ready for email, Slack, or a shared doc