stakeholder-update
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.
Security Assessment
About stakeholder-update
Stakeholder Update generates a status or announcement tailored to a specific audience and cadence, translating the same underlying progress into the right framing for each reader. It fits weekly and monthly leadership updates, launch announcements, and one-off escalations of a risk or blocker, and can render the same progress as an exec brief, engineering detail, or customer-facing note. It is invoked as a slash command with the update type and audience.
The workflow first determines the update type (weekly, monthly, launch, or ad-hoc) and then the audience, with distinct treatments for executives/leadership, the engineering team, cross-functional partners, customers/external, and the board. It next pulls context from whatever tools are connected: a project tracker for roadmap and milestone status and at-risk items, a chat integration for decisions and blockers raised in channels, meeting transcription for notes and action items, and a knowledge base for decision documents. If nothing is connected, it asks the user for what was accomplished, current blockers or risks, decisions made or needed, and what is next.
Audience-specific templates drive the output. Executive updates lead with a status color and TL;DR, then progress tied to goals, risks with mitigation, specific asks, and next milestones, kept very brief. Engineering updates list what shipped with links, what is in progress with owners, decisions made or needed, and priority changes. Cross-functional updates emphasize what is coming that affects the partner and what is needed from them by when; customer updates are benefit-framed with no internal jargon; and launch updates cover what shipped, why it matters, scope and limitations, metrics, rollout, and feedback channels. A Green/Yellow/Red status framework guides honest reporting: move to Yellow at the first sign of risk and to Red when escalation is genuinely needed. After drafting, the skill offers to adjust tone, detail, or emphasis, format for the delivery channel, and, if a chat connector is present, draft the message for sending.
FAQ
What audiences can it write for?
Executives/leadership, the engineering team, cross-functional partners, customers/external, and the board, each with its own template and level of detail.
What update types does it support?
Weekly (regular progress), monthly (higher-level trends and milestones), launch announcements, and ad-hoc one-offs such as escalations, pivots, or major decisions.
Where does it get the content from?
From connected tools when available, such as a project tracker, chat, meeting transcription, or knowledge base, or, if none are connected, from details you provide about accomplishments, blockers, decisions, and next steps.
How does the status framework work?
It uses Green (on track), Yellow (at risk), and Red (off track), advising you to move to Yellow at the first sign of risk and to Red when you have exhausted your own options and need escalation.
How long should an executive update be?
Very brief. The guidance targets roughly under 200 to 300 words, leading with the conclusion and only including risks you actually want help with.
Install stakeholder-update
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
anthropics/knowledge-work-plugins