Skip to content
Back to skills

Stakeholder Communication

ASecurity

Use when updating the stakeholder - report in outcome language (what changed for users, what's next, what decision is needed), translate technical detail, and surface risks early

  • 109 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 19, 2026
ai-agentsgoperformance

Security analysis

A100/100

Scanned October 2, 2026

npx -y skills add makifbaysal/tasktrooper --skill stakeholder-communication --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Stakeholder Communication?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Stakeholder Communication
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/makifbaysal-stakeholder-communication/badge)](https://www.skillsdirectory.com/skills/makifbaysal-stakeholder-communication)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: stakeholder-communication
category: pm
description: Use when updating the stakeholder - report in outcome language (what changed for users, what's next, what decision is needed), translate technical detail, and surface risks early
source: anthropics/knowledge-work-plugins stakeholder-update (Apache-2.0), adapted
---
# Stakeholder Communication

## Overview

The stakeholder cares about outcomes, not mechanics. The failure modes are forwarding raw technical detail and reporting risks only once they've already hurt.

**Core principle:** Outcome language, and bad news early.

## Rules

- Report what changed for users, what's next, and what decision (if any) is needed.
- **Translate, don't forward.** "Fixed an N+1 in the task query" → "The board now loads quickly on large projects."
- **Bad news early:** report a risk when you detect it, not when it materializes.

## Structure

```
Done since last update: <user-facing outcomes>
In progress:            <what's being built now>
Blocked / needs you:    <the decision required, if any>
```

## Decision-request format

When the update needs a decision, don't just flag it — frame it so one reply resolves it:

```
Decision needed: <the one-sentence question>
Options:         (a) <option> — <one-line tradeoff>
                 (b) <option> — <one-line tradeoff>
Recommendation:  <a> because <reason>
If no answer by <when>: <what happens — e.g. "work stays queued behind it">
```

## Worked Example

Raw: "TaskExporter has an N+1; QA bounced it; the architect flagged a missing index."

Reported: "Export is close but held in review — a performance issue on large projects is being fixed now (no action needed). Everything else from this batch is done. Next up is the mobile export button; I'll need you to confirm the filename format when we get there."

## Common Mistakes

- Forwarding jargon (N+1, nil deref, migration).
- A "green" update that hides a known risk.
- Reporting a slip only after the deadline passed.

## Red Flags

- The update contains a term a non-engineer wouldn't understand.
- A risk you knew about last update surfaced as a surprise this update.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…