stakeholder-comms

Generate audience-specific stakeholder communications with status, risk, and decision frameworks.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/aimentor606/aether --skill stakeholder-comms-aimentor606
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stakeholder-comms
Source: https://github.com/aimentor606/aether/tree/main/core/kortix-master/opencode/skills/GENERAL-KNOWLEDGE-WORKER/stakeholder-comms
Command: npx skills add https://github.com/aimentor606/aether --skill stakeholder-comms-aimentor606

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Product teams struggle to communicate progress, risks, and decisions with different audiences using the right level of detail, format, and ask; this Skill standardizes those communications so stakeholders stay informed, aligned, and able to act.

Core Features & Use Cases

  • Audience-specific templates: Ready-made formats for executive summaries, engineering updates, cross-functional partner notes, and customer communications that prioritize what each audience cares about.
  • Status & risk frameworks: Green/Yellow/Red guidance, when to escalate, and ROAM risk classification to make issues visible and actionable.
  • Decision documentation and meeting facilitation: ADR template, meeting agendas, retros, and demo guidance to capture context, rationale, and next steps for repeatability.
  • Use Case: Create a one-page executive update that concisely surfaces progress against OKRs, lists top risks with mitigations, and requests a decision with options and a recommended path.

Quick Start

Write an executive status update for Project Apollo summarizing current status, three progress highlights, top two risks with mitigations, and any decisions needed by next Tuesday.

Frequently Asked Questions about stakeholder-comms

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

FAQPage Schema
How do I write an executive status update that surfaces risks and requests a decision?

Stakeholder communication for product initiatives uses audience-specific templates to structure progress, risks, and asks. It applies executive summaries, cross-functional partner notices, and ADR decision formats to keep stakeholders aligned and able to act.

What is the ROAM risk classification framework for status updates?

The ROAM risk classification framework categorizes project issues during stakeholder communication to make them visible and actionable. It guides when to escalate problems within status updates, ensuring risks are properly mitigated or resolved by the right teams.

How do I document decisions and meeting outcomes for product initiatives?

To document decisions and meeting outcomes, use an ADR template alongside meeting facilitation guidance. This captures the context, rationale, and next steps for product initiatives, ensuring repeatability and clear decision documentation for cross-functional partners.

When should I escalate a project risk in an engineering update?

You should escalate a project risk in an engineering update when the status color framework indicates a yellow or red condition. The stakeholder communication framework provides guidance on when issues require executive escalation based on their ROAM classification and impact.

Can I use these templates for both customer-facing announcements and internal cross-functional notices?

Yes, you can use these templates for both customer-facing announcements and internal cross-functional notices. The stakeholder communication framework provides ready-made formats that prioritize the specific details and level of detail each distinct audience cares about.