stakeholder-update

Generate stakeholder updates structured by audience, cadence, and progress sections.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stakeholder-update helps you produce clear, audience-specific status communications without rewriting the same progress information from scratch, whether it’s a weekly readout, a launch note, or an escalation.

Core Features & Use Cases

  • Audience- and cadence-aware updates: Generates executive, engineering, cross-functional, customer/external, or board-ready versions for weekly, monthly, launch, or ad-hoc situations.
  • Structured progress reporting: Organizes updates with consistent sections like TL;DR, risks, decisions needed, asks, and next milestones.
  • Connected-context prompting: Uses connected tools (project tracker, chat, meeting transcription, knowledge base) to pull relevant status, decisions, blockers, and action items.
  • Message-ready formats: Produces updates optimized for delivery channels such as email, chat posts, docs, or slides planning.

Quick Start

Provide the update type and target audience, then ask the skill to generate a stakeholder update using your connected context (or your provided progress, blockers, decisions, and next steps).

Frequently Asked Questions about stakeholder-update

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

FAQPage Schema
How do I generate tailored stakeholder updates for different audiences?

To generate tailored stakeholder updates, provide the update type and target audience, such as leadership, engineering, or cross-functional partners. The skill structures progress, risks, decisions, asks, and next milestones into message-ready formats.

What is the best way to structure weekly status reporting for leadership communication?

The best way to structure weekly status reporting for leadership communication is to use consistent sections like TL;DR, risks, decisions needed, and asks. This ensures exec briefs remain clear and message-ready.

Can I pull context from connected project and chat tools for project communication?

Yes, you can pull context from connected project trackers, chat tools, meeting transcriptions, and knowledge bases to gather relevant status, blockers, and action items for project communication.

Does this approach support ad-hoc risk escalation and product launches?

Yes, this approach supports ad-hoc risk escalation and product launches by structuring updates with consistent sections like TL;DR, risks, decisions needed, and next milestones tailored for each specific scenario.

What formats are available for stakeholder updates and exec briefs?

Stakeholder updates and exec briefs are produced in message-ready formats optimized for delivery channels such as email, chat posts, docs, or slide planning, ensuring audience-specific status communications are ready to send.

Do I need to manually input progress and blockers for status reporting?

No, you do not need to manually input progress and blockers for status reporting if you have connected project, chat, meeting, or knowledge tools. The skill optionally pulls context from these sources automatically.