stakeholder-update

Generate stakeholder status updates tailored to audience type and reporting cadence.

Updated Sep 15, 2026
One-click install
npx skills add https://github.com/Nadav011/nadavai-claude --skill stakeholder-update-nadav011
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stakeholder-update
Source: https://github.com/Nadav011/nadavai-claude/tree/main/plugins/nadavai/skills/stakeholder-update
Command: npx skills add https://github.com/Nadav011/nadavai-claude --skill stakeholder-update-nadav011

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing status updates for different audiences is repetitive and error-prone: executives want outcomes in under 300 words, engineers want ticket links and blockers, and customers want benefits without jargon. This Skill structures that translation work so the same progress becomes an exec brief, an engineering digest, or a customer announcement without starting from scratch each time. ## Core Features & Use Cases - Audience-specific templates: Prebuilt formats for executives, engineering teams, cross-functional partners, customers, and boards, each with the right level of detail and framing. - Status and risk frameworks: Green/Yellow/Red status guidance, ROAM risk communication, and ADR decision documentation baked into the output. - Tool-aware context gathering: Pulls progress, blockers, and decisions from connected project trackers, chat, meeting transcription, and knowledge bases when available. - Use Case: A product manager needs a weekly exec update, a launch announcement for customers, and an escalation of a slipping milestone. The Skill asks for type and audience, pulls recent progress, and drafts each version with the correct tone, length, and asks. ## Quick Start Ask the assistant to generate a weekly stakeholder update for executives covering this week's shipped features, current risks, and decisions needed by Friday.

Frequently Asked Questions about stakeholder-update

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a weekly status update for executives?

Lead with a TL;DR and a Green/Yellow/Red status, then list progress tied to goals, risks with mitigations, and specific decisions needed with deadlines. Keep the whole update under 300 words and frame everything as outcomes, not activities.

How do I tailor the same project update for different audiences?

Identify the audience first: executives get outcomes and asks, engineers get ticket links and blockers, partners get what affects their team, and customers get benefits without jargon. The Skill provides a separate template for each audience so one set of facts becomes multiple versions.

When should I change a project status from green to yellow?

Move to Yellow at the first sign of risk, not when you are certain things are bad. Yellow means progress is slower than planned or a risk has materialized, and flagging it early gives stakeholders more options to help.

What is the ROAM framework for risk communication?

ROAM classifies risks as Resolved, Owned, Accepted, or Mitigated. Each communicated risk should state the impact, likelihood, mitigation plan, and any specific ask, rather than being buried in good news or presented without a plan.

Can this skill pull status from project trackers or chat tools?

Yes, if project tracker, chat, meeting transcription, or knowledge base connectors are available, it pulls completed items, blockers, and decisions automatically. Without connected tools, it asks you to provide accomplishments, risks, and upcoming work directly.