change-impact
Skill1 starsChanged 24 days agoMITView on GitHub
Assesses people and operational impacts when a transformation changes roles, processes, skills, workload or ways of working.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- marinvch/Cortextheir own version, first seen Nov 1, 2026
- willgt-oss/willgt-skillstheir own version, first seen Nov 1, 2026
- kimgea/agent-kittheir own version, first seen Oct 15, 2026
- Seekers2001/docs-governancetheir own version, first seen Oct 13, 2026
- qshanx/docs-governancetheir own version, first seen Oct 13, 2026
- Quirkybrain/claude-code-swe-frameworktheir own version, first seen Sep 20, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- Seekers2001/docs-governance★ 320same name
- qshanx/docs-governance★ 253same name
- marinvch/Cortex★ 1same name
- Quirkybrain/claude-code-swe-framework★ 1same name
- kimgea/agent-kit★ 0same name
- willgt-oss/willgt-skills★ 0same 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 repository133 other files it gives its agents.
- templates/CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- access-control-auditSkill
- ai-opportunity-scanSkill
- ai-policy-writerSkill
- annual-budget-builderSkill
- application-portfolio-mapSkill
- architecture-fit-checkSkill
- automation-backlogSkill
- benefits-realisationSkill
- board-paperSkill
- bottleneck-removalSkill
- break-even-modelSkill
- budget-variance-analystSkill
- business-continuity-plannerSkill
- business-valuationSkill
- capacity-planningSkill
- case-study-writerSkill
- cash-flow-forecastSkill
- change-adoptionSkill
- channel-profitabilitySkill
- churn-cohort-analysisSkill
- client-handoverSkill
- client-kickoffSkill
- client-profitabilitySkill
- client-relationship-managerSkill
- closeout-packSkill
- compensation-bandsSkill
- competitor-mapperSkill
- contribution-marginSkill
- cost-structure-analystSkill
- crisis-communicationsSkill
- customer-insight-synthesiserSkill
- customer-interview-designerSkill
- customer-journey-mapSkill
- customer-segmenterSkill
- cyber-risk-assessmentSkill
- dashboard-requirements-plannerSkill
- data-lineage-mapperSkill
- data-quality-auditSkill
- decision-logSkill
- decision-memoSkill
- decision-rightsSkill
- delivery-model-selectorSkill
- demand-validatorSkill
- discount-governanceSkill
- discovery-call-facilitationSkill
- discovery-call-prepSkill
- discovery-question-designSkill
- discovery-synthesisSkill
- engagement-outcomesSkill
- evidence-synthesiserSkill
- executive-dashboardSkill
- executive-summarySkill
- fee-settingSkill
- financial-statement-diagnosticSkill
- fundraising-readinessSkill
- funnel-diagnosticSkill
- go-to-marketSkill
- governance-designerSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
1
Distinctive
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 9
Use during design and before rollout planning so affected groups receive proportionate preparation and support.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Change Impact Consultant
When to use it
Use during design and before rollout planning so affected groups receive proportionate preparation and support.
What Claude needs
- Background from client-context.md
- Current and future-state designs
- Stakeholder groups, locations and role profiles
- Planned timing, dependencies and known concerns
Method
- Break the change into specific shifts in process, role, skill and behaviour.
- Map affected groups to each shift and implementation wave.
- Rate impact by magnitude, timing, readiness and business criticality.
- Identify workload peaks, capability gaps and likely resistance sources.
- Define actions across leadership, involvement, learning and support.
- Assign owners and validate impacts with representative scenarios.
Output format
Provide a change-impact matrix, stakeholder heatmap, readiness risks and action plan by group, owner and timing.
Quality checks
- Impacts describe what people must do differently.
- Indirect and cumulative impacts are included.
- Actions are proportionate to impact and readiness.
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.

