stakeholder-communication
Skill0 starsChanged 4 months agoMITView on GitHub
Improve status reporting, escalation, and stakeholder communication for engineering work. Use for updates, blockers, and cross-functional coordination.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- rampstackco/claude-skills-pmtheir own version, first seen Oct 13, 2026
- ai-analyst-lab/ai-analysttheir own version, first seen Sep 10, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- ai-analyst-lab/ai-analyst★ 304same name
- rampstackco/claude-skills-pm★ 4same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository32 other files it gives its agents.
- architect-modeSkill
- architecture-bundleSkill
- code-like-a-localSkill
- decision-making-guardrailsSkill
- decision-recordsSkill
- delivery-bundleSkill
- fable-modeSkill
- finish-the-turnSkill
- incident-response-playbookSkill
- launch-readiness-gateSkill
- lead-developer-modeSkill
- lead-with-outcomeSkill
- lean-tool-useSkill
- migration-refactor-safetySkill
- plan-before-implementationSkill
- pr-and-commit-hygieneSkill
- product-delivery-bundleSkill
- product-minded-engineer-modeSkill
- reliability-bundleSkill
- reliability-incident-modeSkill
- review-quality-gateSkill
- run-guardrails-on-code-changesSkill
- security-bundleSkill
- security-minded-engineer-modeSkill
- senior-operating-systemSkill
- staff-engineering-bundleSkill
- staff-engineer-modeSkill
- surgical-questionsSkill
- systematic-debuggingSkill
- test-disciplineSkill
- truthful-reportingSkill
- verify-by-exercisingSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 21
Call out blockers and the decision needed to unblock them.
- Distinctive: line 22
Avoid vague optimism and avoid burying important risks.
- Distinctive: line 26
Do not report progress without saying what was actually verified.
- Distinctive: line 27
Do not hide a blocker behind general language.
- Distinctive: line 28
Do not leave stakeholders guessing about the next decision or action.
- Distinctive: line 29
Do not over-explain routine work when the reader needs the decision or risk.
- Distinctive: line 31
Use this skill to make updates useful for engineering leaders, partners, and collaborators.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Stakeholder communication
Good engineering work is not only executed well; it is communicated clearly. Status updates should be accurate, timely, and useful to the people making decisions.
Communication principles
- Lead with the outcome, not the process.
- State what changed, what is blocked, and what is next.
- Separate facts from assumptions.
- Be explicit about risk, urgency, and confidence.
For status updates
- Share the current state in plain language.
- Describe the impact on delivery, users, or reliability.
- Call out blockers and the decision needed to unblock them.
- Avoid vague optimism and avoid burying important risks.
Non-negotiables
- Do not report progress without saying what was actually verified.
- Do not hide a blocker behind general language.
- Do not leave stakeholders guessing about the next decision or action.
- Do not over-explain routine work when the reader needs the decision or risk.
Use this skill to make updates useful for engineering leaders, partners, and collaborators.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.