rampstackco/claude-skills / skills/stakeholder-communication
stakeholder-communication
VerifiedCommunicate effectively with stakeholders across functions and seniority levels. Use this skill when writing status updates, preparing executive reviews, sharing technical decisions with non-technical audiences, managing up, communicating bad news, or designing the communication cadence for a project. Triggers on stakeholder update, status report, executive summary, exec review, manage up, communicate bad news, project comms, status meeting, weekly update. Also triggers when a project is going off track and the team needs to communicate it.
| File | Kind | Size |
|---|---|---|
| README.md | markdown | 366 B |
| SKILL.md | skill md | 11.1 KB |
| references/update-templates.md | markdown | 9.6 KB |
references/update-templates.md
View on GitHub# Update Templates
Ready-to-use templates for the most common stakeholder communications. Annotated with what each section is doing.
Adapt to your house style. The structure matters more than the exact wording.
---
## Template 1: Weekly project status
For internal teams, manager, sponsor. Sent same day each week.
```
Subject: [Project] weekly update: [date]
**Status: On track**
We're on plan to ship [milestone] by [date].
This week:
- Shipped [specific outcome]
- Started [specific work], [N]% complete
- Decision: chose [option] for [problem]
Next week:
- Complete [specific work]
- Begin [specific work]
- Review: [decision needed by sponsor]
Risks:
- [Risk]: [what we're doing about it]
Asks:
- [Specific ask, if any]
Detail: [link to project doc]
```
**Annotations:**
- Status indicator (On track / At risk / Off track) is the first thing readers scan
- "This week" is outcomes, not activities
- "Next week" is specific commitments, not vague intentions
- Risks have plans attached
- Asks are explicit and called out
---
## Template 2: At-risk update
When the project is no longer comfortably on track.
```
Subject: [Project] update: at risk for [milestone]
**Status: At risk**
The [milestone] target of [date] is at risk because [specific reason].
What's happening:
- [Fact 1]
- [Fact 2]
- [Fact 3]
Impact:
- If we miss by a week: [specific impact]
- If we miss by a month: [specific impact]
What we're doing:
- [Action 1] (owner: [name], by: [date])
- [Action 2] (owner: [name], by: [date])
What we need from you:
- [Specific decision or help]
Next update: [date]
```
**Annotations:**
- Doesn't pretend to be on track
- Names the specific cause
- Quantifies the impact
- Has a plan with owners and dates
- Has a clear ask
- Sets expectations for next update
---
## Template 3: Off-track / missed milestone
When the milestone has been missed or will be.
```
Subject: [Project] off track: [milestone] will miss [date]
**Status: Off track**
We will miss the [date] milestone for [specific reason]. Revised target: [new date].
What happened:
[2-3 sentences of what specifically caused the miss. Direct, no euphemisms.]
Impact:
- [Specific impact 1]
- [Specific impact 2]
What we're doing:
- [Action 1]
- [Action 2]
Lessons we're applying:
- [Lesson learned]
What we need:
- [Specific ask, if any]
Next milestone: [date for the next checkpoint]
```
**Annotations:**
- States the miss in the headline
- Names cause without scapegoating
- Quantifies impact
- Has a plan
- Includes lessons (shows learning, builds trust)
- Sets the next checkpoint
---
## Template 4: Decision request
When you need a decision from a stakeholder.
```
Subject: Decision needed: [decision] by [date]
**The decision:** [What needs to be decided]
**Context (60 seconds):**
[The minimum needed for someone to understand. Include only what's relevant.]
**Options:**
Option A: [Name]
- What: [Description]
- Pros: [List]
- Cons: [List]
- Cost / time: [Specific]
Option B: [Name]
- What: [Description]
- Pros: [List]
- Cons: [List]
- Cost / time: [Specific]
Option C: [Name]
- What: [Description]
- Pros: [List]
- Cons: [List]
- Cost / time: [Specific]
**Recommendation:** Option [X], because [reason].
**Need by:** [Date]
**Detail:** [Link to fuller analysis]
```
**Annotations:**
- The decision is named at the top
- Context is bounded (60 seconds)
- Options are parallel in structure
- Recommendation is explicit
- Deadline is named
---
## Template 5: Executive review
For exec audiences: monthly, quarterly, or per major milestone.
```
Subject: [Initiative] exec review: [date]
**Headline:** [One-sentence summary of the state of things]
**Key points:**
1. [Point 1 with one supporting sentence]
2. [Point 2 with one supporting sentence]
3. [Point 3 with one supporting sentence]
**Metrics:**
| Metric | Target | Actual | Trend |
|---|---|---|---|
| [Metric 1] | [Target] | [Actual] | ↑/↓/→ |
| [Metric 2] | [Target] | [Actual] | ↑/↓/→ |
| [Metric 3] | [Target] | [Actual] | ↑/↓/→ |
**Decisions needed:**
- [Decision 1: brief context, options summary, recommendation]
- [Decision 2: brief context, options summary, recommendation]
**Risks:**
- [Top risk and mitigation]
**Asks:**
- [Specific ask]
**Detail:** [Link to fuller documentation]
```
**Annotations:**
- Executives skim. Headline carries the load.
- 3 key points (not 7)
- Metrics in table form, with trend
- Decisions called out, with recommendations
- Detail is linked, not inlined
- One page max for the email body
---
## Template 6: Launch announcement (internal)
For announcing something shipped.
```
Subject: Launched: [Thing]
We've launched [Thing].
What it is:
[1-2 sentences of plain description. What it does, who it's for.]
Why it matters:
[1-2 sentences of impact. What problem it solves, what changes.]
How to learn more:
- [Link to docs / demo / page]
- [Contact for questions]
Thanks to:
[The team that did the work, by name]
```
**Annotations:**
- Short and clear
- Includes the why (not just the what)
- Acknowledges the team
---
## Template 7: Asking for help
When you need expertise, time, or introduction from a colleague.
```
Subject: [Specific ask]: [N] minutes
Hi [Name],
I'm working on [brief context, one sentence]. I'd value your help with [specific ask].
What I need:
- [Specific item 1]
- [Specific item 2]
What I've already tried:
- [Approach 1, outcome]
- [Approach 2, outcome]
Time I'm asking for: [N minutes / specific session / specific deliverable]
Need by: [Date or "no rush"]
If you're not the right person, who would you suggest?
Thanks,
[Name]
```
**Annotations:**
- Subject is specific
- Specific ask, not vague
- Shows you've tried (respect for their time)
- States time required
- Provides an out (suggest someone else)
---
## Template 8: Update for skip-level / VP
For your manager's manager. Shorter, sharper than direct-manager update.
```
Subject: [Initiative]: quick update
[Initiative] is [on track / at risk] for [milestone].
Highlights:
- [Outcome 1]
- [Outcome 2]
- [Decision: what was decided]
What's coming:
- [Next big milestone]
Risks I'm watching:
- [Top risk]
I'll come to you for: [specific upcoming need]
Detail: [link]
```
**Annotations:**
- Half the length of a manager update
- Emphasizes outcomes, not activities
- "I'll come to you for" sets expectations on when you'll need them
- Detail is linked, not inlined
---
## Template 9: Quarterly business review (QBR)
Cross-functional, leadership audience. Substantive.
```
Subject: [Function/team] QBR: Q[N]
**Quarter at a glance:**
[3-sentence narrative summarizing the quarter]
**Goals vs results:**
| Goal | Target | Result | Status |
|---|---|---|---|
| [Goal 1] | [Target] | [Result] | ✅ / 🟡 / ❌ |
| [Goal 2] | [Target] | [Result] | ✅ / 🟡 / ❌ |
| [Goal 3] | [Target] | [Result] | ✅ / 🟡 / ❌ |
**Wins this quarter:**
- [Specific win 1]
- [Specific win 2]
- [Specific win 3]
**What didn't go as planned:**
- [Specific miss 1: what happened, what we learned]
- [Specific miss 2: what happened, what we learned]
**Next quarter:**
- [Top priority 1]
- [Top priority 2]
- [Top priority 3]
**Risks and asks:**
- [Risk and what we're doing]
- [Ask if any]
**Headcount / budget changes:**
[If relevant, brief]
```
**Annotations:**
- Narrative summary up front
- Goals table with clear pass/fail
- Wins AND misses (honest)
- Forward-looking section
- Asks are explicit
---
## Template 10: Bad news, broader audience
For when something significant has gone wrong and a wider audience needs to know.
```
Subject: [Plain description of what happened]
[1 sentence: what happened, in plain language]
What happened:
[2-4 sentences of specific facts. No euphemisms.]
Who's affected:
- [Specific group 1]
- [Specific group 2]
Impact:
- [Specific impact 1]
- [Specific impact 2]
What we've done so far:
- [Action 1]
- [Action 2]
What's next:
- [Action and timeline]
- [Action and timeline]
If you have questions:
[Contact and channel]
[Sign-off from named accountable person, with their role]
```
**Annotations:**
- Plain subject. No spin.
- Facts before reassurance
- Impact stated, not hedged
- Forward path is clear
- Named accountable person at the bottom
- Channel for questions
---
## What to avoid in any template
**Vague status indicators.** "Things are going well" is not status. On track / at risk / off track is.
**Activity dumps.** "We met. We reviewed. We updated." Stakeholders care about what changed, not what you did.
**Hedge words on certainty.** "We should probably maybe be on track." If you know, say it. If you don't, say what you don't know.
**Buried asks.** Asks at the bottom in a paragraph go unread. Pull them out. Bold them. Make them findable.
**Different units in different sections.** "5 days" in one place, "by next Tuesday" in another. Pick a convention and stick with it.
**Acronyms not understood by the audience.** Especially across functions. Spell out on first use.
**No links.** Detail in the email forces everyone to read the same wall of text. Link the detail. Let people choose.
**Missing accountable owner.** Who owns each next step? If the answer is "the team," nothing happens. Name people.
**Inconsistent cadence.** Update Monday, then nothing for three weeks, then a wall on a Friday. Set cadence. Hold it.
---
## Customizing for your context
The templates above are starting points. Customize for:
- Your organization's tone (formal vs casual)
- Your stakeholders' preferences (some want bullets, some want narrative)
- Your medium (email vs doc vs slide)
- Your project's complexity (more or less detail in the body)
Whatever you customize, keep:
- Headline first
- Status indicator visible
- Asks explicit
- Owners and dates named
- Consistent structure across updates (so readers can scan reliably)
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |