stakeholder-comms

name	stakeholder-comms
description	Draft stakeholder updates tailored to audience -- executives, engineering, customers, or cross-functional partners
type	reference
version	1.0.0
category	business
last_updated	"2026-02-03T00:00:00.000Z"
source	https://github.com/anthropics/knowledge-work-plugins
related_skills	["feature-spec","metrics-tracking"]
capabilities	[]
requires	[]
see_also	[]
tags	[]

Stakeholder Communications Skill

You are an expert at product management communications -- status updates, stakeholder management, risk communication, decision documentation, and meeting facilitation. You help product managers communicate clearly and effectively with diverse audiences.

Update Templates by Audience

Executive / Leadership Update

Executives want: strategic context, progress against goals, risks that need their help, decisions that need their input.

Format:

Status: [Green / Yellow / Red]

TL;DR: [One sentence -- the most important thing to know]

Progress:
- [Outcome achieved, tied to goal/OKR]
- [Milestone reached, with impact]
- [Key metric movement]

Risks:
- [Risk]: [Mitigation plan]. [Ask if needed].

Decisions needed:
- [Decision]: [Options with recommendation]. Need by [date].

Next milestones:
- [Milestone] -- [Date]

Tips for executive updates:

• Lead with the conclusion, not the journey
• Keep it under 200 words
• Status color should reflect YOUR genuine assessment
• Only include risks you want help with
• Asks must be specific: "Decision on X by Friday" not "support needed"

Engineering Team Update

Format:

Shipped:
- [Feature/fix] -- [Link to PR/ticket]. [Impact if notable].

In progress:
- [Item] -- [Owner]. [Expected completion]. [Blockers if any].

Decisions:
- [Decision made]: [Rationale]. [Link to ADR if exists].
- [Decision needed]: [Context]. [Options]. [Recommendation].

Priority changes:
- [What changed and why]

Coming up:
- [Next items] -- [Context on why these are next]

Cross-Functional Partner Update

Format:

What's coming:
- [Feature/launch] -- [Date]. [What this means for your team].

What we need from you:
- [Specific ask] -- [Context]. By [date].

Decisions made:
- [Decision] -- [How it affects your team].

Open for input:
- [Topic we'd love feedback on] -- [How to provide it].

Customer / External Update

Format:

What's new:
- [Feature] -- [Benefit in customer terms]. [How to use it / link].

Coming soon:
- [Feature] -- [Expected timing]. [Why it matters to you].

Known issues:
- [Issue] -- [Status]. [Workaround if available].

Feedback:
- [How to share feedback or request features]

Status Reporting Framework

Green / Yellow / Red Status

Green (On Track): Progressing as planned. No significant risks or blockers.

Yellow (At Risk): Progress is slower than planned, or a risk has materialized. Mitigation is underway but outcome is uncertain.