agentleFS
Sign inStart free
Tngc93Tngc93/product-management-skills/skills/stakeholder-update/SKILL.md

stakeholder-update

Skill0 starsChanged 33 days agoMITView on GitHub

Write a short status update for stakeholders (executives, a steering group, partner teams or the whole team) from notes, task lists, metrics or a changelog, leading with what changed and what decisions are needed. Use when the user asks for a status update, weekly or monthly update, progress report, steering committee note, release summary or "update for my manager".

18 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use experiment-designer, launch-readiness and 3 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Dokkabei97Skill

    experiment-designer

    Designs A/B tests and product experiments with hypothesis structuring, sample size calculation, duration estimation, and result interpretation. Unified framework for both product and marketing experiments.

    Also in 3 projects that use this

  • pratikshadakeSkill

    launch-readiness

    Audits whether a feature or product is truly ready for launch with a structured checklist and readiness status (Ready/At Risk/Not Ready). Use before any product launch to catch critical gaps.

    Also in 3 projects that use this

  • OpenAISkill

    market-sizing

    Estimate market, segment, or opportunity size with transparent assumptions and uncertainty. Use for TAM/SAM/SOM, sizing scenarios, or comparing the scale of possible opportunities.

    Also in 3 projects that use this

  • MetaSkill

    roadmap

    Build, continue, inspect, or visualize a source-grounded mathematical roadmap and theorem DAG in an existing Autoform Markdown blueprint. Use for source research, repository-wide inventories of existing and planned mathematics, scope, coverage, milestones, and roadmap articles; do not create repository infrastructure or prove Lean declarations.

    Also in 3 projects that use this

  • dillonluiSkill

    design-review

    Review a view or flow for UX and UI issues. Provides severity-ranked, actionable findings grounded in established design heuristics. Use when the user asks for design feedback, UX review, or UI critique.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 18 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask, or infer from the request: who reads it (executive, peer team, own team), how often they get updates, and what they decide.

    line 14
  2. Distinctive:

    Write in the reader's language.

    line 31
  3. Very specific:

    Run pm-skills lint <file> --type update.

    line 35

“Common” is measured: kept by at least 6 in 10 of the 18 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Write a stakeholder update

Readers skim. In the first three lines they should learn whether things are on track, what changed since last time and what you need from them. Everything after that is supporting detail.

CLI: node "${CLAUDE_PLUGIN_ROOT}/cli/pm-skills.mjs" (or ../../cli/pm-skills.mjs relative to this file). Below, pm-skills.

1. Know the reader

Ask, or infer from the request: who reads it (executive, peer team, own team), how often they get updates, and what they decide. Executives need status, risks and asks. Partner teams need dates and dependencies. The team needs context and recognition.

2. Gather facts

From the material the user gave: what shipped, what moved on the metrics (with numbers and the comparison period), what slipped and why, what is next with dates, and what is blocked. Do not round bad news into good news. If a date moved, say from when to when.

3. Write it

Start from pm-skills template stakeholder-update.

  • Status in one word: On track, At risk or Off track. Choose honestly; "At risk" early is cheaper than "Off track" late.
  • TL;DR: two or three sentences that stand on their own.
  • Progress: outcomes, not activity. "Checkout errors down from 3.2% to 1.1%" beats "worked on checkout".
  • Next: the next two or three milestones with dates.
  • Risks and blockers: each with impact and what is being done about it.
  • Asks: specific decisions or help, from a named person, by a date. If there are none, say so.
  • Under 250 words for executives. Link to details instead of pasting them.
  • Write in the reader's language; match the tone of the user's earlier updates if they shared one.

4. Check

Run pm-skills lint <file> --type update. It checks that summary, progress, next, risks and asks are all present and flags vague words.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free