stakeholder-comms

Draft audience-specific stakeholder updates with structured sections for progress, risks, decisions, and next steps.

Updated Feb 9, 2026
One-click install
npx skills add https://github.com/nsalvacao/nsalvacao-claude-code-plugins --skill stakeholder-comms
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stakeholder-comms
Source: https://github.com/nsalvacao/nsalvacao-claude-code-plugins/tree/main/plugins/product-management/skills/stakeholder-comms
Command: npx skills add https://github.com/nsalvacao/nsalvacao-claude-code-plugins --skill stakeholder-comms

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Product managers often struggle to craft clear, consistent updates for executives, engineers, customers, and cross-functional partners.

Core Features & Use Cases

  • Templates and guidance for audience-specific updates (executives, engineering, customers, cross-functional partners)
  • Structured formats covering status, risks, decisions, and next steps to improve clarity and alignment
  • Best-practice tips for tone, cadence, and concise storytelling in product discussions

Quick Start

Provide the audience and purpose, and I will draft a concise stakeholder update.

Frequently Asked Questions about stakeholder-comms

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

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

Drafting audience-specific stakeholder updates requires structured formats for executives, engineering, customers, or cross-functional partners. You provide the audience and purpose, and the Skill generates a concise update with clear sections for progress, risks, decisions, and next steps.

What is the best way to structure a weekly status update for executives?

The best way to structure a weekly status update for executives is using a template with clear sections covering progress, risks, decisions, and next steps. This ensures concise storytelling and improves clarity and alignment in product discussions.

How do I communicate project risks and decisions to cross-functional partners?

To communicate project risks and decisions to cross-functional partners, use audience-specific templates that highlight status, risks, decisions, and next steps. This structured formatting ensures clear alignment and concise storytelling across product teams.

Can I use a single template for both customer launch announcements and engineering reports?

A single template is not ideal for both customer launch announcements and engineering reports. The Skill provides distinct audience-specific guidance, adjusting tone, cadence, and structured formatting to suit executives, engineering, customers, or cross-functional partners.

What should I include in a monthly stakeholder report for product discussions?

A monthly stakeholder report for product discussions should include structured sections for progress, risks, decisions, and next steps. Applying best-practice tips for tone and concise storytelling ensures the update is clear and aligned with the intended audience.