stakeholder-communication-planner
Skill28 starsChanged 8 months agoMITView on GitHub
In this repository105 other files it gives its agents.
- acceptance-criteria-writerSkill
- ambiguity-hunterSkill
- as-is-process-investigatorSkill
- assumption-extractorSkill
- assumptions-constraints-logSkill
- benefit-hypothesis-writerSkill
- breakout-structure-designerSkill
- business-problem-framingSkill
- business-rule-extractorSkill
- catwoe-root-definitionSkill
- constraint-detectorSkill
- critical-thinking-bias-checkSkill
- definition-of-done-drafterSkill
- deliverable-consistency-checkSkill
- edge-case-elicitorSkill
- evidence-gap-reviewSkill
- functional-vs-nonfunctional-splitterSkill
- interview-designSkill
- moscow-prioritisationSkill
- observation-study-planSkill
- pestle-analysisSkill
- porters-five-forcesSkill
- power-interest-gridSkill
- probe-question-generatorSkill
- problem-statement-refinerSkill
- process-modelling-and-improvementSkill
- process-model-specSkill
- proto-requirements-normalizerSkill
- prototype-elicitationSkill
- pyramid-funnel-diamond-interviewerSkill
- questionnaire-designSkill
- questionnaire-pilot-checkerSkill
- raci-matrixSkill
- raci-rasci-builderSkill
- requirements-conflict-checkerSkill
- requirements-elicitationSkill
- requirements-gap-auditorSkill
- requirements-interrogatorSkill
- requirements-packagerSkill
- requirements-prioritizerSkill
- requirements-quality-checkSkill
- requirements-traceability-starterSkill
- see-i-clarifierSkill
- ssm-analysisSkill
- stakeholder-analysisSkill
- stakeholder-registerSkill
- strategy-analysisSkill
- swot-prioritisationSkill
- to-be-process-designerSkill
- use-case-specificationSkill
- value-proposition-analysisSkill
- workshop-designSkill
- acceptance-criteria-writerSkill
- ambiguity-hunterSkill
- as-is-process-investigatorSkill
- assumption-extractorSkill
- assumptions-constraints-logSkill
- benefit-hypothesis-writerSkill
- breakout-structure-designerSkill
- business-problem-framingSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
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 36
Call out overload risk, silence risk, and bypass risk.
- Distinctive: line 50
Prefer structured outputs over loose prose.
- Distinctive: line 55
Do not pretend weak evidence is confirmed fact.
- Distinctive: line 56
Do not confuse stakeholder opinion with validated rule or process truth.
- Distinctive: line 57
Do not hide missing coverage behind polished wording.
- Distinctive: line 58
Do not flatten politically different stakeholders into one generic audience.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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-planner
Purpose
Define what each stakeholder group needs to know, when they need it, and how they should be engaged through the analysis lifecycle.
Trigger this skill when
- Stakeholder engagement is likely to drift or become ad hoc.
- You need a deliberate communication approach before workshops or discovery sessions.
- There are multiple audiences with different information needs.
Expected inputs
- stakeholder map
- power-interest matrix
- project timeline
- decision points
Deliverables
- communication plan
- cadence recommendations
- owner suggestions
- engagement risks
Operating procedure
- Segment stakeholders by information need, timing, influence, and required level of involvement.
- Map each segment to a cadence, channel, format, and owner.
- Separate decision communication from status communication.
- Identify moments that require consultation, sign-off, or escalation.
- Call out overload risk, silence risk, and bypass risk.
Quality gates
- Plan is stakeholder-specific instead of one broadcast cadence for everyone.
- Decision points and sign-off moments are explicit.
- Communication risks are visible.
Handoff targets
- workshop-agenda-builder
- interview-plan-designer
- project-charter-writer if present
Output style
- Be explicit about uncertainty.
- Prefer structured outputs over loose prose.
- Separate confirmed findings, inferred findings, and open questions.
- Preserve source context where practical.
Failure modes to avoid
- Do not pretend weak evidence is confirmed fact.
- Do not confuse stakeholder opinion with validated rule or process truth.
- Do not hide missing coverage behind polished wording.
- Do not flatten politically different stakeholders into one generic audience.
Minimum output skeleton
## Summary
## Findings
## Structured outputs
## Risks or tensions
## Open questions
## Recommended next skillDoes 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.

