← Back to Skills

SKILL · workflow

Stakeholder Communication Architect

Audience-calibrated messaging for different stakeholders. Transforms the same information into messages tailored for executives (business impact), engineers (technical detail), clients (value delivered), or team (actionable next steps). Produces ready-to-send drafts with tone, length, and emphasis matched to the recipient's priorities and communication style.

komunikacjainteresariuszezarządzanieinterpersonalneprzywództwopisanie

Install as Claude Code skill

Drop into ~/.claude/skills/<name>/SKILL.md

.skill

Stakeholder Communication Architect

What This Skill Does

Same information, different audiences. This skill transforms a single update, decision, or proposal into messages calibrated for each stakeholder type. The output is ready-to-send drafts — not templates, actual messages.

Audience Profiles

Executive / C-Suite

  • Cares about: Business impact, risk, timeline, cost
  • Doesn't care about: Implementation details, tech stack choices
  • Tone: Confident, concise, decision-oriented
  • Length: 3-5 sentences max. If longer, lead with a TL;DR
  • Format: Bullet points, bold key numbers, clear ask

Technical Lead / Architect

  • Cares about: Architecture decisions, trade-offs, technical risk, dependencies
  • Doesn't care about: Business fluff, marketing language
  • Tone: Precise, honest about trade-offs
  • Length: As detailed as needed
  • Format: Technical specifics, diagrams if helpful, links to docs

Client / External Stakeholder

  • Cares about: Value delivered, timeline, what changes for them
  • Doesn't care about: Internal process, your team struggles
  • Tone: Professional, reassuring, proactive
  • Length: Medium — enough to build confidence, not so much it's overwhelming
  • Format: Progress highlights, next steps, any actions required from them

Team / Direct Reports

  • Cares about: What to do next, context for decisions, blockers cleared
  • Doesn't care about: Political maneuvering, corporate positioning
  • Tone: Direct, transparent, supportive
  • Length: Detailed enough to be actionable
  • Format: Action items, context, timeline, who owns what

Manager / Upward

  • Cares about: Are we on track? Any risks I should know? Do you need anything?
  • Tone: Proactive, structured, solution-oriented (raise problems with proposed solutions)
  • Length: Concise but complete
  • Format: Status, risks (with mitigation), asks (specific)

Process

  1. Gather the raw information — what happened, what was decided, what's next
  2. Identify audiences — who needs to know, and why
  3. For each audience: a. Filter: what from the raw info matters to them? b. Frame: how does it relate to their priorities? c. Draft: write the actual message in their preferred format d. Channel: suggest where to send it (email, Slack, meeting, doc)
  4. Review — check for consistency across messages (same facts, different framing)

Output Format

## Communication Plan: {topic}

### To: {CEO / CTO / Client / Team}
**Channel:** Slack DM / Email / Meeting
**When:** Immediately / Today / After {event}
**Message:**

{Ready-to-send draft}

---

### To: {next stakeholder}
...

Anti-Patterns

  • Sending the same message to everyone (executives don't read technical details, engineers don't trust business fluff)
  • Hiding bad news behind jargon
  • Making the recipient guess what you need from them
  • Over-communicating status that nobody asked for
  • Under-communicating risk because it's uncomfortable