stakeholder-update

Generate audience- and cadence-aware stakeholder updates with status colors and role-specific sections.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/ngochuy13/intern-dev --skill stakeholder-update-ngochuy13
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stakeholder-update
Source: https://github.com/ngochuy13/intern-dev/tree/main/skills/stakeholder-update
Command: npx skills add https://github.com/ngochuy13/intern-dev --skill stakeholder-update-ngochuy13

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Producing clear, audience-appropriate stakeholder updates is time-consuming and often inconsistent, especially when you need to cover progress, risks, decisions, and next milestones for different readers.

Core Features & Use Cases

  • Audience- and cadence-aware drafting: Creates updates for weekly, monthly, launch, or ad-hoc situations while matching the expected level of detail.
  • Status clarity (G/Y/R) with risk framing: Guides you to select and justify a status color and communicate risks with mitigation and specific asks.
  • Role-specific structures: Tailors output for executives, engineering, cross-functional partners, customers, and boards using the appropriate template and tone.
  • Context sourcing guidance: Tells you how to pull the right facts from connected tools (project tracker, chat, meeting transcription, knowledge base) or what to provide when tools aren’t connected.

Quick Start

Tell the skill the update type and target audience (e.g., weekly leadership, launch announcement to customers, or ad-hoc risk escalation to executives) and provide the key accomplishments, blockers/risks, decisions needed, and what’s coming next.

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 stakeholder update for executives?

To write a stakeholder update for executives, provide key accomplishments, blockers, decisions needed, and next steps. The skill tailors the output with role-specific structures and a status color framework to keep the executive brief scannable.

What is the best way to format a weekly leadership status report?

The best way to format a weekly leadership status report is using a cadence-aware structure that includes progress, risks, decisions, and upcoming milestones. It applies a Green/Yellow/Red status color framework to justify project health and communicate risk mitigations.

How do I communicate project risks and mitigation to a board?

Communicating project risks to a board requires tailoring the update with role-specific structures and tone. You must frame risks with specific mitigations and asks, while selecting and justifying a status color to provide clear, scannable context for board members.

Can I generate a launch announcement for customers from project tracker data?

Yes, you can generate a launch announcement for customers by providing the update type and target audience. The skill guides you to pull the right facts from connected tools like a project tracker or knowledge base, or allows you to supply details manually if tools aren't connected.

Do I need connected tools to draft an ad-hoc risk escalation?

No, you do not need connected tools to draft an ad-hoc risk escalation. The skill provides context sourcing guidance, prompting you for required details like key accomplishments and blockers directly when tools such as a project tracker or chat are not connected.