stakeholder-communication

Adapt PM artifacts into audience-specific cuts for executives, customers, engineering, and sales.

3|2|Updated Aug 24, 2026
One-click install
npx skills add https://github.com/hero-engine/hero --skill stakeholder-communication-hero-engine
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: stakeholder-communication
Source: https://github.com/hero-engine/hero/tree/main/domains/pm/skills/stakeholder-communication
Command: npx skills add https://github.com/hero-engine/hero --skill stakeholder-communication-hero-engine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product managers often send one generic summary of a PRD or roadmap update to every audience, forcing executives, customers, engineers, and sales reps to dig through irrelevant detail. This Skill provides the discipline for cutting the same artifact differently per audience without distorting the underlying facts. ## Core Features & Use Cases - Four Audience Cuts: Rules for what executives, customers, engineering, and sales each want, what to lead with, and what to omit. - The "So What" Pressure-Test: A sentence-level check ensuring every exec-facing line ties to an outcome, tradeoff, or decision rather than activity filler. - Working-Backwards Awareness: Guidance on when a moment calls for a full PR-FAQ or six-page narrative, deferring the format mechanics to dedicated skills. - Use Case: You finished a PRD for a CSV export feature. Use this Skill to produce an exec cut leading with the measurable outcome, a customer cut leading with capability and timing, an engineering cut with acceptance criteria, and a sales cut tied to buyer objections. ## Quick Start Summarize this PRD into separate executive, customer, engineering, and sales updates using the stakeholder-communication skill.

Frequently Asked Questions about stakeholder-communication

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

FAQPage Schema
How do I summarize a PRD differently for executives and engineers?▼

Cut the same artifact per audience: lead executives with the measurable outcome and tradeoff, and lead engineering with context, acceptance criteria, constraints, and dependencies. The facts stay identical; only the lead, omissions, and frame change.

What should an executive product update include?▼

An executive update should lead with the measurable outcome, the bet behind it, and what was given up. Every line must survive the "so what" test by tying to an outcome, tradeoff, or decision; activity-only lines like "we shipped the refactor" get cut.

When should I use a PR-FAQ or six-page narrative instead of a summary?▼

Reach for the working-backwards format when a bet needs a full narrative case, such as a major launch, strategic pivot, or leadership decision that turns on the story. One-page audience cuts cannot carry that kind of decision.

What are common mistakes in stakeholder communication for product managers?▼

Common anti-patterns include sending one cut to all audiences, quoting different dates to different audiences, turning internal updates into marketing copy, and filling exec updates with activity lines that lack outcomes.

Can I change facts or dates for different audiences?▼

No. Shape the framing, never the facts. Quoting a conservative date to one audience and an aggressive one to another for the same work is sandbagging, and fabricated quotes or metrics are prohibited in any cut.