# AI Stakeholder Translator

> Multi-audience communication multiplexer. Takes ONE product update, decision, or launch plan and generates 5 perfectly tailored versions for different stakeholders (engineering, executive, board, customer, sales) simultaneously.

- Skill: `varunk130/ai-stakeholder-translator` (Agent Skill)
- Install (CLI): `npx skillmds@latest add varunk130/ai-stakeholder-translator`
- Raw SKILL.md: https://api.skillmd.com/api/skills/varunk130/ai-stakeholder-translator/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- Author: varunk130 (https://skillmd.com/u/varunk130)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/varunk130/ai-stakeholder-translator

---


# Stakeholder Translator - One Input, Five Outputs

You receive ONE piece of product information and produce FIVE precisely tailored communications - each optimized for its audience's priorities, vocabulary, metrics preference, and attention span.

## Process

### Step 1: Intake & Core Message Extraction
1. Core fact (1 sentence)
2. Impact magnitude
3. Timeline
4. Key metrics (business vs technical)
5. Risk/sensitivity scan

### Step 2: Sensitivity Classification
- All audiences: shipped features, public benchmarks
- Internal only: timelines, resource constraints, internal metrics
- Restricted: unreleased roadmap dates, revenue numbers

### Step 3: Generate All Five Outputs

**OUTPUT 1: Engineering Team Update** - Slack, 5-10 bullets, technical, direct

**OUTPUT 2: Executive Summary** - Email/DM, 3-5 sentences, outcome-oriented, max 150 words

**OUTPUT 3: Board Deck Narrative** - Slide (30 words max) + speaker notes (100 words max), thesis-driven

**OUTPUT 4: Customer-Facing Changelog** - 1 paragraph, benefit-oriented, zero jargon

**OUTPUT 5: Sales Enablement Brief** - Elevator pitch + talking points + objection handling + competitive positioning

## Quality Checklist
- All five outputs convey the SAME core facts
- Each uses vocabulary appropriate to its audience
- No restricted content leaked into customer or sales outputs
- Executive summary under 150 words
- Board narrative connects to a strategic theme
- Customer changelog has zero internal jargon
- Sales brief has at least 2 objection-handling pairs