stakeholder-translatorlisted

# Stakeholder Translator Transform a single product update into five audience-tailored communications — each with the right tone, detail level, technical depth, and framing. Includes sensitivity classification so you know what's shareable. ## Output Save to `outputs/stakeholder-[topic]-[YYYY-MM-DD].md` ## When to Use - Writing a product update that needs to reach multiple audiences - Preparing exec summaries alongside engineering updates - Creating board narratives from sprint outcomes - Generating customer changelogs without leaking internal details - Arming sales with talk tracks and objection handling ## What You'll Get Five distinct communications from one input: | Output | Audience | Framing | |--------|----------|---------| | **Engineering Update** | Dev team | Technical decisions, code references, debt trade-offs | | **Executive Summary** | Leadership | Business impact, metrics, decisions needed | | **Board Narrative** | Board of Directors | Strategic positioning, speaker notes | | **Customer Changelog** | End users | Benefits-focused, no internal details | | **Sales Enablement** | Sales team | Objection handling, competitive positioning, talk tracks | Plus: - **Sensitivity Classification** for each section (✅ Safe / ⚠️ Caution / 🔒 Internal Only) - **Key Message Consistency Check** — ensures the core narrative is coherent across all five versions ## Process ### Step 1: Collect the Update I'll ask for: > "What's the product update? Paste your internal notes, s