Stakeholder Update
- 4 installs
- 3 repo stars
- Updated August 5, 2026
- broomva/skills
stakeholder-update is a Claude skill that turns one set of project facts into three audience-specific versions: technical, business-impact, and customer-facing.
About
stakeholder-update is a Claude skill that takes one set of project facts and generates three tailored versions: technical for engineering, business-impact for leadership, and customer-facing for success teams. A developer uses it when the same update must reach different audiences at the right level of detail. Each version stands alone and follows a fixed markdown template. It reframes provided facts without inventing new ones.
- Turns one set of project facts into three audience versions
- Produces technical, business-impact, and customer-facing variants
- Never invents facts, only reframes what is provided
Stakeholder Update by the numbers
- 4 all-time installs (skills.sh)
- Ranked #2,331 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
stakeholder-update capabilities & compatibility
- Capabilities
- stakeholder update · status report
- Use cases
- copywriting · project management
- Pricing
- Free
What stakeholder-update says it does
One set of facts → three audience-specific versions.
Never invent facts — only reframe what's provided
Each version should stand alone — a reader shouldn't need the other versions
npx skills add https://github.com/broomva/skills --skill stakeholder-updateAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 4 |
|---|---|
| repo stars | ★ 3 |
| Last updated | August 5, 2026 |
| Repository | broomva/skills ↗ |
What it does
Turn a single set of project facts into technical, leadership, and customer-facing update versions.
Who is it for?
Communicating a single project update to engineering, leadership, and customers at once.
Skip if: Generating new facts; it only reframes what the user provides.
When should I use this skill?
Writing an update or translating the same information for different audiences.
What you get
Three stand-alone update versions from a single fact set.
- Technical version
- Business-impact version
- Customer-facing version
By the numbers
- Generates three audience-specific versions from one fact set
Files
Stakeholder Update
One set of facts → three audience-specific versions.
Workflow
1. Gather the facts — Accept raw project facts from the user. These can be:
- A list of bullet points
- A technical doc or PR description
- A conversation summary
- A vault note path
2. Extract the core — Identify:
- What changed (the facts)
- Why it matters (the impact)
- What's next (the action items)
- Any risks or blockers
3. Generate three versions:
Version 1: Technical (Engineering)
- Lead with what changed technically
- Include relevant code/architecture details
- Reference PRs, commits, or technical docs
- Use precise technical language
- Focus on: implementation details, technical debt, performance metrics
Version 2: Business Impact (Leadership)
- Lead with business outcome
- Translate technical changes to business metrics
- Include timeline and resource implications
- Use clear, jargon-free language
- Focus on: revenue impact, risk reduction, strategic alignment, timeline
Version 3: Customer-Facing (Success Teams)
- Lead with user benefit
- Explain changes in terms of user experience
- Include any action items for customers
- Use friendly, accessible language
- Focus on: what's better for users, when they'll see it, what they need to do
Output Format
## Stakeholder Update: [Topic]
**Date**: [YYYY-MM-DD]
**Author**: [name]
---
### Technical Version (Engineering)
**TL;DR**: [one sentence]
[2-4 paragraphs with technical detail]
**Action items**:
- [ ] [engineering action]
---
### Business Version (Leadership)
**TL;DR**: [one sentence focused on business outcome]
[2-3 paragraphs, no jargon]
**Key metrics**:
- [metric]: [before] → [after]
**Action items**:
- [ ] [leadership action]
---
### Customer-Facing Version (Success Teams)
**TL;DR**: [one sentence focused on user benefit]
[2-3 paragraphs, friendly tone]
**Customer action required**: [yes/no + details]
**Talking points for support**:
1. [key point to communicate]
2. [key point to communicate]Behavior
- Never invent facts — only reframe what's provided
- If the input is too sparse for three versions, ask for more context
- Each version should stand alone — a reader shouldn't need the other versions
- Match the formality level to the audience
- Save to vault if requested:
vault/updates/stakeholder-[topic]-[YYYY-MM-DD].md
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.691k196kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.585k196k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.493kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.493kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).493kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.493kFAQ
How many versions does it produce?
Three: technical for engineering, business-impact for leadership, and customer-facing for success teams.
Will it add facts I did not provide?
No. The skill only reframes provided facts and asks for more context if the input is too sparse.