stakeholder-update
Write a concise, evidence-based stakeholder update for product, engineering, operations, research, or program work. Use for weekly update, status report, executive summary, project update, risk update
Files1
View on GitHubSKILL.mdskills/common/stakeholder-update/SKILL.md
GitHubStakeholder Update
Communicate decisions, evidence, risks, and asks without hiding uncertainty.
- Identify audience, decision rights, cadence, and the few metrics or outcomes that matter.
- Lead with outcome and change since the last update.
- Report progress, evidence, risks/blockers, decisions needed, owners, and next checkpoints.
- Use Green/Yellow/Red only with an explicit evidence basis and a concrete recovery or escalation action.
- Separate confirmed facts, forecasts, and requests.
Do not pad updates with activity lists, invent status confidence, or send externally without approval.