Menu

Individual skill

stakeholder-update

0upvotes

Writes project stakeholder updates readable in under 60 seconds - honest RAG status, decisions made, explicit asks with owners and dates, next milestones - tiered to the audience. Use when someone asks "write my weekly project update", "how do I tell stakeholders we're at risk", "draft a status email for leadership", or "my updates get ignored, fix the format". Do NOT use for aggregating many teams' statuses into one engineering-wide report - use eng-status-rollup instead. For monthly investor letters with metrics and asks to VCs, use investor-update-writer; for customer-facing incident status, use status-page-update.

skills/stakeholder-update/SKILL.md

Read pinned source

Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
24
Repository last updated
Oct 13, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Stakeholder Update

Stakeholders are busy and skim. A good update answers their questions before they ask them, in under 60 seconds of reading. The costly failure is the buried blocker: the ask that sat in paragraph four for three weeks, unread, until the project went red and the stakeholder's first question was "why am I hearing this now?"

## Inputs to collect

1. Audience tier (see below) - this decides length and vocabulary before anything else.
2. Honest status: on track, at risk, or off track - and the one thing driving that call.
3. Decisions made since the last update, with who made them.
4. Asks: what is needed, from whom, by when. If there are none, confirm that is really true.
5. Next 2-3 milestones with target dates.
6. Cadence and send time - same day, same time, every time.

## Audience tiering
Back to top