stakeholder-communication — Claude Code skill: updates and hard talks
A skill for planning stakeholder communication: status updates, engagement plans and conversations about slipping deadlines.
npx skills add aj-geddes/useful-ai-prompts --skill stakeholder-communication -a claude-codeWhat stakeholder-communication does
The skill breaks project communication into pieces: who cares about the work, who holds influence, and what each group should hear. It ships an engagement model that runs from unaware to champion, with a note on how to treat each level. For executive sponsors, for instance, it suggests starting with a monthly summary.
Four guides sit in the references/ directory: stakeholder analysis, communication planning, status update templates and difficult conversations. The quick start is Python — a StakeholderAnalysis class listing stakeholder categories, their interests and influence. The snippet cuts off partway, so the full implementation lives in the guides.
Reach for it when scope, timeline or budget shifts, when a risk needs escalation, or when a new stakeholder joins. One caveat: this is a set of practices and templates, not a ready tool. You still fill in the details about your own stakeholders.
What it helps with
- draft a communication plan for a project
- write a status update for leadership
- prepare for a talk about a slipped deadline
- map stakeholders by influence and interest
- escalate a risk without blindsiding the client
Example prompts for the agent
- help me draft a communication plan for the project
- write a monthly update for the executive sponsor
- prepare talking points for a hard conversation about moving the release
How to install stakeholder-communication
1Skills CLI (Vercel)
npx skills add aj-geddes/useful-ai-prompts --skill stakeholder-communication -a claude-code2Manually: put the files in place
~/.claude/skills/stakeholder-communication/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/stakeholder-communication/
1Skills CLI (Vercel)
npx skills add aj-geddes/useful-ai-prompts --skill stakeholder-communication -a codex2Manually: put the files in place
.agents/skills/stakeholder-communication/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add aj-geddes/useful-ai-prompts --skill stakeholder-communication -a cursor2Manually: put the files in place
.cursor/skills/stakeholder-communication/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install aj-geddes/useful-ai-prompts stakeholder-communication2Manually: put the files in place
.github/skills/stakeholder-communication/SKILL.md1Skills CLI (Vercel)
npx skills add aj-geddes/useful-ai-prompts --skill stakeholder-communication -a gemini-cli2Platform CLI
gemini skills install https://github.com/aj-geddes/useful-ai-prompts --path skills/stakeholder-communicationManually: put the files in place
.devin/skills/stakeholder-communication/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add aj-geddes/useful-ai-prompts --skill stakeholder-communication -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about stakeholder-communication
How do I install stakeholder-communication in Claude?
Run npx skills add aj-geddes/useful-ai-prompts --skill stakeholder-communication -a claude-code. The skill lands in ~/.claude/skills/stakeholder-communication/SKILL.md.
What does stakeholder-communication do?
It helps run project communication: stakeholder analysis, an update plan, status report templates and prep for difficult conversations.
Which platforms does the skill support?
Besides Claude, there are install paths for Codex, Cursor, GitHub Copilot, Gemini CLI and OpenCode.
Source text
SKILL.md · MIT
---
name: stakeholder-communication
description: >
Manage stakeholder expectations and engagement through targeted communication,
regular updates, and relationship building. Tailor messaging for different
stakeholder groups and priorities.
---
# Stakeholder Communication
## Table of Contents
- [Overview](#overview)
- [When to Use](#when-to-use)
- [Quick Start](#quick-start)
- [Reference Guides](#reference-guides)
- [Best Practices](#best-practices)
## Overview
Effective stakeholder communication ensures alignment, manages expectations, builds trust, and keeps projects on track by addressing concerns proactively.
## When to Use
- Project kickoff and initiation
- Weekly/monthly status updates
- Major milestone achievements
- Changes to scope, timeline, or budget
- Risks or issues requiring escalation
- Stakeholder onboarding
- Handling difficult conversations
## Quick Start
Minimal working example:
```python
# Stakeholder identification and engagement planning
class StakeholderAnalysis:
ENGAGEMENT_LEVELS = {
'Unaware': 'Provide basic information',
'Resistant': 'Address concerns, build trust',
'Neutral': 'Keep informed, demonstrate value',
'Supportive': 'Engage as advocates',
'Champion': 'Leverage for change leadership'
}
def __init__(self, project_name):
self.project_name = project_name
self.stakeholders = []
def identify_stakeholders(self):
"""Common stakeholder categories"""
return {
'Executive Sponsors': {
'interests': ['ROI', 'Strategic alignment', 'Timeline'],
'communication': 'Monthly executive summary',
'influence': 'High',
'impact': 'High'
},
'Project Team': {
// ... (see reference guides for full implementation)
```
## Reference Guides
Detailed implementations in the `references/` directory:
| Guide | Contents |
|---|---|
| [Stakeholder Analysis](references/stakeholder-analysis.md) | Stakeholder Analysis |
| [Communication Planning](references/communication-planning.md) | Communication Planning |
| [Status Communication Templates](references/status-communication-templates.md) | Status Communication Templates |
| [Difficult Conversations](references/difficult-conversations.md) | Difficult Conversations |
## Best Practices
### ✅ DO
- Tailor messages to stakeholder interests and influence
- Communicate proactively, not reactively
- Be transparent about issues and risks
- Provide regular scheduled updates
- Document decisions and communication
- Acknowledge stakeholder concerns
- Follow up on action items
- Build relationships outside crisis mode
- Use multiple communication channels
- Celebrate wins together
### ❌ DON'T
- Overcommunicate or undercommunicate
- Use jargon stakeholders don't understand
- Surprise stakeholders with bad news
- Promise what you can't deliver
- Make excuses without solutions
- Communicate through intermediaries for critical issues
- Ignore feedback or concerns
- Change communication style inconsistently
- Share inappropriate confidential details
- Communicate budget/timeline bad news via email
© aj-geddes · MIT · aj-geddes/useful-ai-prompts