Localized reading guide
stakeholder-updatePurpose, usage and source
Generate a stakeholder update tailored to audience and cadence. Use when writing a weekly or monthly status for leadership, announcing a launch, escalating a risk or blocker, or translating the same progress into exec-brief, engineering-detail, or customer-facing versions.
Source retrieved:
- Source repository
- anthropics/knowledge-work-plugins
- SKILL.md
product-management/skills/stakeholder-update/SKILL.md- Repository stars
- 34,049
- Repository updated
- 2026-10-30
- Categories
- Business
- Last collected
License: License file needs review
Workflow excerpts are reading aids, not executable instructions from Codez. No third-party Skill was run to produce this page.
The purpose and workflow passages below are upstream material, organized and translated for reading. They are distinct from the separately labeled Codez editorial analysis.
What this Skill does
Generate a stakeholder update tailored to audience and cadence. Use when writing a weekly or monthly status for leadership, announcing a launch, escalating a risk or blocker, or translating the same progress into exec-brief, engineering-detail, or customer-facing versions.
How the upstream workflow works
When to Change Status
Move to Yellow at the FIRST sign of risk, not when you are sure things are bad Move to Red when you have exhausted your own options and need escalation Move back to Green only when the risk is genuinely resolved, not just paused Document what changed when you change status — "Moved to Yellow because [reason]"
Upstream passage · L211 ↗When to Write an ADR
Strategic product decisions (which market segment to target, which platform to support) Significant technical decisions (architecture choices, vendor selection, build vs buy) Controversial decisions where people disagreed (document the rationale for future reference) Decisions that constrain future options (choosing a technology, signing a partnership)
Upstream passage · L266 ↗Stakeholder Update
> If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md. Generate a stakeholder update tailored to the audience and cadence.
Upstream passage · L7 ↗/stakeholder-update $ARGUMENTSRequirements and setup
No short requirements passage was selected from this file. This does not mean the Skill has no dependencies. Check the repository setup instructions and referenced files.
Limits and quality checks
No separate limits passage was selected from this file. This does not mean the Skill is safe for every input or environment. Review the complete source and validate your own result.
Start with a safe trial
- Check the supported host and the repository installation instructions. Keep the Skill directory and its referenced scripts, assets and documentation together; SKILL.md alone may omit dependencies.
- Give the agent your real input, desired output and acceptance criteria. Invocation syntax and available tools depend on the host; this site does not assume a universal install command.
- Try the source workflow in a disposable project or on a copy. Review operations that change files, remote services or billable resources before allowing them.
- Validate the output against the source quality checks and your own requirements. A successful trigger or a high repository Star count does not establish a correct result.
Read further in the source
- Stakeholder Update
- 1. Determine Update Type
- 2. Determine Audience
- 3. Pull Context from Connected Tools
- 4. Generate the Update
- 5. Review and Deliver
- Executive / Leadership Update
- Engineering Team Update
- Cross-Functional Partner Update
- Customer / External Update
- Green / Yellow / Red Status
- When to Change Status
- ROAM Framework for Risk Management
- Communicating Risks Effectively
- Common Mistakes in Risk Communication
- Architecture Decision Record Format
- When to Write an ADR
- Tips for Decision Documentation
- Stand-up / Daily Sync
- Sprint / Iteration Planning
- Retrospective
- Stakeholder Review / Demo
- Output Format
- Tips
Related Skills
Translation and scope
This reading guide selects passages from the pinned upstream SKILL.md. Translation is assisted. It is not a complete manual or a claim of tested compatibility. Read the original and its referenced files before use.
This introduction refers to the pinned version below; current repository activity and collection time are shown separately.
- Pinned source
- Read the original ↗
- Source retrieved
- Source commit
2574e29377c7173d0cecffef29a6ecbd7f8ccb5d- Source SHA-256
bcdb8ee95dc34d025dcc3d98e7435c4dca45930581b3b7a8707f8770dd364e79