stakeholder-comms

Write audience-specific program updates and validate staged Slack drafts for delivery.

Updated Jul 28, 2026
One-click install
npx skills add https://github.com/christian-byrne/comfy-skills --skill stakeholder-comms-christian-byrne
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: stakeholder-comms
Source: https://github.com/christian-byrne/comfy-skills/tree/main/skills/stakeholder-comms
Command: npx skills add https://github.com/christian-byrne/comfy-skills --skill stakeholder-comms-christian-byrne

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Sending one status update to every audience leaves most readers with nothing actionable, eroding your communication channel. This Skill structures program updates per audience—engineering, leadership, support, finance, GTM, and affected users—so each recipient gets the content they need to act. ## Core Features & Use Cases - Audience Matrix: Maps each audience to what they want, what to omit, and the action they should take, with a decision-first message structure. - Queue Hygiene & Delivery Lifecycle: Classifies queued messages by recipient action (decide, do, know, communicate, none) and tracks delivery states (staged, sent, answered, superseded) with reply-cursor reconciliation. - Slack Draft Validation: Ships a Python script that checks paste-ready Slack drafts for hard-wrapped paragraphs, unsupported bold, bare GitHub/Linear identifiers, and raw URLs. - Use Case: You have 147 staged Slack drafts in Notion. Use this Skill to triage them into send-as-owner, FYI, cancel-expired, and answer-needed classes, then run the validator before publishing. ## Quick Start Ask the AI to draft a status update about your program tailored separately for leadership, engineering, and support using the stakeholder-comms skill.

Frequently Asked Questions about stakeholder-comms

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

FAQPage Schema
How do I write a status update for multiple audiences?▼

Write separate updates per audience rather than reformatting one message. Use the audience matrix to determine what each group wants, what to omit, and what action they should take, then lead with the decision or ask.

How to validate Slack message drafts before sending?▼

Run the included validate_slack_drafts.py script against your Markdown queue file. It checks for hard-wrapped paragraphs, unsupported double-asterisk bold, raw URLs, and bare GitHub or Linear identifiers that must be hyperlinked.

What should an executive summary include versus an engineering update?▼

Leadership needs the decision required, risk to date, tradeoff, and one number—omit implementation detail and ticket IDs. Engineering needs what changed, what breaks, and what to do differently—omit business framing.

Why do stakeholders stop reading status updates?▼

Updates fail when they contain no action for the reader, bury the ask after long context, or repeat weekly with no state change. Match cadence to actual state changes and include an 'if you do nothing' consequence line.

When should I escalate instead of sending a status update?▼

Escalate when you need a decision: send it to one person or forum with options and a required-by date. Do not bury decision requests inside broadcast updates, where they get read as information.