change-management
Skill11 starsChanged 16 days agoMITView on GitHub
Use when a proposal must address adoption, resistance, readiness, communications, transition, or organisational reform. Unlike capacity-building, this skill governs behaviour and operating-model change rather than teaching competencies alone.
15 other projects use a version of this.
Adopted by
Most recently taken up by
- itential/infra-agent-skillstheir own version, first seen Nov 15, 2026
- darkweb19/skillstheir own version, first seen Nov 8, 2026
- aymardkouakou/claude-gh-skillstheir own version, first seen Nov 8, 2026
- Happy-Technologies-LLC/happy-platform-skillstheir own version, first seen Nov 1, 2026
- anotb/management-consulting-plugintheir own version, first seen Nov 1, 2026
- edu6565/claude-skillstheir own version, first seen Oct 11, 2026
Used with
Projects with it also use andreessen, business-investment-advisor and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
Hussain-ElfalahSkillandreessen
Also in 4 projects that use this
Hussain-ElfalahSkillbusiness-investment-advisor
Also in 4 projects that use this
csiddhant796-blipSkillkarpathy-coder
Use when writing, reviewing, or committing code to enforce Karpathy's 4 coding principles — surface assumptions before coding, keep it simple, make surgical changes, define verifiable goals. Triggers on "review my diff", "check complexity", "am I overcomplicating this", "karpathy check", "before I commit", or any code quality concern where the LLM might be overcoding.
Also in 4 projects that use this
csiddhant796-blipSkillself-eval
Honestly evaluate AI work quality using a two-axis scoring system. Use after completing a task, code review, or work session to get an unbiased assessment. Detects score inflation, forces devil's advocate reasoning, and persists scores across sessions.
Also in 4 projects that use this
- +8 more from Hussain-Elfalah
Other versions15 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 15
- anotb/management-consulting-plugin★ 62same name
- Happy-Technologies-LLC/happy-platform-skills★ 41same name
- abinauv/business-consulting★ 28same name
- Hassaan146/claude-skills★ 18same name
- 10Legs/ceo-f500-harness★ 8same name
- Hussain-Elfalah/Agentic-Skills★ 2same name
- JohnnyQ-commits/aqueduct-data-agent★ 2same name
- aymardkouakou/claude-gh-skills★ 1same name
- itential/infra-agent-skills★ 1same name
- mahiunfiltered/claude-code-skills★ 1same name
5 more not listed
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 repository101 other files it gives its agents.
- AGENTS.mdAGENTS.md
- skills/profiles-sectors/sectors/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- ai-agent-commercial-packagingSkill
- ai-agent-contract-language-packSkill
- ai-agent-intervention-credit-and-abort-refundSkill
- ai-agent-msa-and-sla-addendum-templatesSkill
- ai-agent-procurement-objections-on-commercialsSkill
- ai-agent-renewal-and-true-upSkill
- ai-agent-sla-and-credit-scheduleSkill
- ai-agent-success-fee-and-outcome-pricingSkill
- ai-agent-business-case-and-roiSkill
- ai-agent-change-management-and-adoptionSkill
- ai-agent-compliance-credentialsSkill
- ai-agent-discovery-and-qualificationSkill
- ai-agent-methodologySkill
- ai-agent-poc-and-pilot-scopingSkill
- ai-agent-pricing-and-packaging-proposalSkill
- ai-agent-procurement-and-questionnaireSkill
- ai-agent-risk-and-responsible-aiSkill
- ai-agent-team-compositionSkill
- ai-agent-vertical-positioningSkill
- ai-on-saas-business-case-and-roiSkill
- ai-on-saas-change-management-and-adoptionSkill
- ai-on-saas-combined-methodologySkill
- ai-on-saas-compliance-credentialsSkill
- ai-on-saas-discovery-and-qualificationSkill
- ai-on-saas-poc-and-pilot-scopingSkill
- ai-on-saas-pricing-and-packaging-proposalSkill
- ai-on-saas-procurement-and-questionnaireSkill
- ai-on-saas-risk-and-responsible-aiSkill
- ai-on-saas-team-compositionSkill
- ai-on-saas-vertical-positioningSkill
- accounting-finance-advisorySkill
- business-analysis-toolsSkill
- capacity-buildingSkill
- consulting-frameworksSkill
- data-managementSkill
- eac-ecommerce-bds-programme-designSkill
- environmental-and-social-safeguardsSkill
- gender-and-social-inclusionSkill
- giz-eu-local-procurement-responseSkill
- monitoring-and-evaluationSkill
- project-managementSkill
- retail-transformation-proposalSkill
- risk-managementSkill
- stakeholder-engagementSkill
- sustainability-planningSkill
- east-african-englishSkill
- language-standardsSkill
- ai-slop-auditSkill
- anti-ai-slopSkill
- bid-red-team-dual-reviewSkill
- kaizen-improvement-systemSkill
- operational-readiness-and-localisationSkill
- skill-safety-auditSkill
- skill-writingSkill
- submission-proof-and-receipt-disciplineSkill
- update-claude-documentationSkill
- 01-cover-letterSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
17 rules. 0 are common, 17 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 12 edited versions we read keep these.
17
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 17
Use this skill when the assignment explicitly needs change-management, adoption, transition, or resistance-management content.
- Distinctive: line 32
Stop or block the workflow when a required input, permission, or acceptance basis is missing.
- Distinctive: line 35
Read the local references only where they materially improve the output.
- Distinctive: line 41
Keep the approach specific to the client context and implementation reality.
- Distinctive: line 63
Read and search are required.
- Distinctive: line 67
If interviews, surveys, usage data, or sponsor access are unavailable, provide a provisional stakeholder hypothesis and …
- Distinctive: line 97
Retraining cadence is communicated: when models / prompts are updated, what users see change, what the rollback path is, who signed off.
- Distinctive: line 108
Use PDCA/QC Story during transition.
- Distinctive: line 131
When the ToR asks for a standalone change management plan
- Distinctive: line 145
When to use: ICT system rollouts, process redesign, new policy implementation, any assignment where end-user adoption determines success.
- Distinctive: line 151
Create urgency — evidence of need for change
- Distinctive: line 160
When to use: public sector reform, institutional restructuring, multi-ministry programmes, assignments where the change is cultural and …
- Distinctive: line 170
When to use: as a complementary lens alongside ADKAR or Kotter, particularly when the assignment involves staff retrenchment, role …
- Distinctive: line 200
Never dismiss resistance as "people don't like change" — there is always a specific reason
- Distinctive: line 201
Document resistance patterns and responses for the client's future reference
- Distinctive: line 213
When the ToR asks for a dedicated change management plan, generate a document covering:
- Distinctive: line 225
Follow east-african-english standards throughout.
“Common” is measured: kept by at least 6 in 10 of the 12 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 Management
Acknowledgement: Shared by Peter Bamuhigire, techguypeter.com, +256 784 464178.
<!-- dual-compat-start -->Use When
- Use this skill when the assignment explicitly needs change-management, adoption, transition, or resistance-management content.
- Load it when another proposal section needs this domain expertise.
Do Not Use When
- The task only needs formatting or proposer-profile selection.
- Another supporting skill is a closer fit for the assignment.
Required Inputs
| Artefact | Source | Required? | If absent |
| Defined change, affected groups, sponsor, and implementation plan | Client or proposal lead | required | Stop detailed planning and return discovery questions. |
| Readiness, incentives, constraints, and prior-change evidence | Interviews, surveys, client records | conditional | State hypotheses and propose a readiness assessment. |
Workflow
Stop or block the workflow when a required input, permission, or acceptance basis is missing. Recover by revising the scope, obtaining evidence, or returning the narrowest qualified draft before proceeding.
- Identify where change-management logic matters in the assignment.
- Identify adoption risks across leaders, managers, frontline staff, users, customers, beneficiaries, and support teams.
- Read the local references only where they materially improve the output.
- Convert the guidance into proposal-ready activities, controls, and adoption mechanisms.
- Integrate the result into the target section and check for consistency.
Quality Standards
- Translate theory into practical proposal language, outputs, and roles.
- Keep the approach specific to the client context and implementation reality.
- Preserve compatibility with existing repository workflows and file paths.
Anti-Patterns
- Naming ADKAR or Kotter without actions. Fix: map each activity to a group, owner, timing, and measure.
- Treating communication as adoption. Fix: add readiness, practice, reinforcement, and support.
- Describing resistance as a staff defect. Fix: identify incentives, workload, trust, and process causes.
- Launching all users at once without evidence. Fix: stage pilots and define go/no-go criteria.
- Promising human review without an accountable queue. Fix: name authority, SLA, escalation, and audit evidence.
Outputs
| Artefact | Consumer | Acceptance condition |
| Change and adoption plan | Evaluator, sponsor, line managers | Identifies groups, readiness, interventions, owners, measures, decision gates, and reinforcement. |
Evidence Produced
| Evidence | Consumer | Acceptance condition |
| Readiness and adoption register | Segmented table | Each material adoption risk has evidence, owner, response, indicator, and review point. |
Capability and Permission Boundaries
Read and search are required; any edit or external action remains within the explicit authority and permission boundary stated below. Analysis is read-only by default. Draft or edit artefacts only when authorised; do not send staff communications, change access, or activate operational changes without named client approval.
Degraded Mode
If interviews, surveys, usage data, or sponsor access are unavailable, provide a provisional stakeholder hypothesis and readiness-assessment plan. Do not claim readiness or adoption.
Decision Rules
| Change condition | Action | Risk avoided |
| Individual system or process adoption | Apply ADKAR by affected group | Generic organisation-wide activity |
| Institution-wide reform | Apply Kotter with governance gates | Sponsor-free programme |
| High uncertainty or trust risk | Pilot, measure, and stage authority | Premature full rollout |
Worked Example
For a case-management system, segment clerks, supervisors, and administrators; pilot one office; measure task completion and override causes; then expand after support capacity is evidenced.
SaaS Mindset Transition
For SaaS implementation engagements, the change management workstream must address four substantive operating-model shifts beyond the standard ADKAR/Kotter material:
- Per-customer to per-tenant operations: operations no longer manages dedicated environments per customer; it manages tenant lifecycles inside a shared platform.
- Scheduled per-customer releases to continuous releases for all tenants: release management becomes continuous; per-customer release waivers are not granted.
- Installation services to customer success engagement: the team that used to install software for each new customer becomes the customer-success team that engineers adoption, value realisation, and expansion.
- Perpetual licence to recurring subscription: finance, sales, and contracts reorganise around recurring revenue, deferred revenue recognition, renewal forecasting, and expansion planning.
Each shift is named, measured, communicated, trained, and reinforced through the change-management workstream. Reference ../saas-pilot-to-rollout-change-management/SKILL.md for the SaaS-specific change skill.
AI Mindset Transition
For AI-on-SaaS engagements, layer on the AI mindset transition alongside the SaaS shifts:
- Trust before authority: AI authority is staged — shadow, confirm, supervised auto, full auto — not granted at launch. Trust-building activities are designed into adoption.
- Augment vs replace, honestly: the framing is agreed before user communications. Honest framing protects adoption; sugar-coated "augment" framing breaks trust irreversibly when the intent is to replace.
- Human-in-the-loop is engineered, not promised: HITL names the human, the authority (approve, decline, modify), the SLA, the queue, the audit, and the escalation. "Human review" is not HITL.
- Retraining cadence is communicated: when models / prompts are updated, what users see change, what the rollback path is, who signed off. Silent retraining destroys trust.
- Override and abstain are measured, not feared: override rate (5–25 % healthy) and abstain-correctness (≥ 0.95) are dashboard metrics signed off at the AI Governance Forum.
Reference ../ai-on-saas-change-management-and-adoption/SKILL.md for the companion skill and ../references/ai-on-saas-change-management-playbook.md for the long-form playbook.
<!-- dual-compat-end -->Continuity, cutover, stabilisation, and lessons gates
When the change includes a site move, system transition, process migration, or service handover, add a continuity gate: charter and decision rights; current-state inventory; readiness evidence; critical-service fallback; timed cutover and rollback; first-day monitoring; stabilisation exit criteria; and closeout lessons. Do not promise go-live readiness because training or procurement is complete; require evidence for access, data, safety, communication, support, acceptance, and residual-risk ownership.
Use PDCA/QC Story during transition. Record the baseline, failure mode, smallest countermeasure, guardrail, owner, result, and standardisation decision. Keep immediate service continuity and longer-term organisational learning as separate workstreams when a disruption is material.
References
- Proposal skills router for repository-wide routing and mandatory quality gates.
- Local
references/files when detailed frameworks or examples are needed. - ../references/service-design-methodology-module.md for co-creation, prototype validation, service implementation, and frontline adoption.
- ../references/discovery-question-bank-for-proposals.md for change-readiness, adoption, and implementation assumption questions.
- ../references/saas-multi-tenant-architecture-block.md for the SaaS mindset paragraph and the four substantive shifts.
- ../references/saas-customer-success-engagement-package.md for the customer-success function that replaces installation services.
- ../references/saas-lifecycle-email-program-proposal-template.md for the lifecycle communications that support adoption.
- ../customer-service-and-maintenance-proposals/SKILL.md when adoption depends on support, issue handling, and post-launch confidence.
- ../saas-pilot-to-rollout-change-management/SKILL.md - SaaS-specific change management skill.
- ../ai-on-saas-change-management-and-adoption/SKILL.md - AI-on-SaaS change and adoption skill.
- ../references/ai-on-saas-change-management-playbook.md - AI adoption playbook (trust staging, augment-vs-replace, HITL, retraining cadence).
Most consulting assignments — ICT implementations, institutional reform, process improvement — require people to change how they work. Proposals that address this explicitly score higher than those that treat change as an afterthought. This skill provides the OCM frameworks and structures that proposal sections draw from.
When to Read This Skill
- The assignment involves a new system, process, or institutional structure
- The ToR mentions "change management", "adoption", "transition", or "organisational readiness"
- Drafting methodology sections for ICT implementations, reform programmes, or restructuring
- When the ToR asks for a standalone change management plan
Frameworks
ADKAR (Preferred for System and Process Changes)
The most practical framework for East African consulting proposals — easy to explain to non-specialists and maps directly to proposal activities:
- Awareness — why the change is happening (stakeholder communication, town halls, leadership messaging)
- Desire — willingness to participate (early adopter engagement, addressing "what's in it for me", involving staff in design)
- Knowledge — how to change (training programmes, user guides, help desks)
- Ability — demonstrated capability (hands-on practice, mentoring, supervised go-live)
- Reinforcement — sustaining the change (performance monitoring, recognition, feedback loops, corrective action)
When to use: ICT system rollouts, process redesign, new policy implementation, any assignment where end-user adoption determines success.
Kotter's 8-Step Model (Preferred for Large Institutional Reform)
More suited to multi-year reform programmes and institutional transformation:
- Create urgency — evidence of need for change
- Build a guiding coalition — senior champions and change agents
- Form a strategic vision — clear picture of the desired future state
- Enlist a volunteer army — broad engagement beyond the project team
- Enable action — remove barriers, provide resources and authority
- Generate short-term wins — visible early results to build momentum
- Sustain acceleration — build on wins, do not declare victory too early
- Institute change — embed in policies, procedures, job descriptions, performance metrics
When to use: public sector reform, institutional restructuring, multi-ministry programmes, assignments where the change is cultural and structural, not just procedural.
Bridges' Transition Model (Complementary)
Useful for addressing the human side of change — particularly in contexts where staff fear job losses or role changes:
- Ending — acknowledge what is being lost (old processes, familiar tools, established routines)
- Neutral zone — support people through the uncertainty (clear communication, temporary support structures)
- New beginning — reinforce the benefits of the new state (quick wins, recognition, career development)
When to use: as a complementary lens alongside ADKAR or Kotter, particularly when the assignment involves staff retrenchment, role redefinition, or significant cultural shift.
Common Change Management Activities for Proposals
Stakeholder Readiness Assessment
- Identify stakeholder groups affected by the change
- Assess current readiness (awareness, willingness, capability) per group
- Map resistance factors and enablers
- Design targeted interventions per group
Change Champion Network
- Identify and recruit change champions from within the client organisation
- Train champions on the change narrative and their role
- Establish regular champion meetings for feedback and issue escalation
- Champions serve as the bridge between the project team and end users
Communication Plan
| Audience | Message | Channel | Frequency | Responsible |
| Senior management | Strategic progress, decisions needed | Steering committee | Monthly | Team Leader |
| Middle management | Operational impact, timeline, support available | Workshops, email | Bi-weekly | Change Lead |
| End users | What is changing, when, and how to prepare | Town halls, posters, SMS | Weekly during transition | Change Champions |
Resistance Management
- Identify sources of resistance early — do not wait for go-live
- Distinguish between resistance due to lack of information (address with communication) and resistance due to genuine concerns (address with participation and design adjustments)
- Never dismiss resistance as "people don't like change" — there is always a specific reason
- Document resistance patterns and responses for the client's future reference
Reference Files
Load these reference files for deeper guidance when writing change management sections:
- references/change-process-models.md — Satir Change Model, Lewin, Kübler-Ross change curve, force field analysis, Nadler-Tushman congruence model, Burke-Litwin diagnostic, complexity and emergence (Hearsum), Silver Bullet lifecycle, Adams and Straw's Seven Fundamental Shifts, types-of-change classification
- references/hard-and-soft-integration.md — hard/soft integration principle, project charter for change, four-team model (core project, change management, transition monitoring, red team), RACI matrix, communication plan framework, training plan framework (four-level evaluation), resistance management plan (seven sources of resistance, change saturation analysis, resistance patterns), action review, organisational readiness assessment (eight dimensions with scoring)
- references/lean-and-adaptive-change.md — Lean Change Management cycle (Insights→Options→Experiments), improvement canvas, strategic change canvas, one-page change plan, change agent network design, digital change management (adoption curve, six practices), feedback-driven vs plan-driven comparison, measuring change success (qualitative, quantitative, leading vs lagging indicators)
Generating a Standalone Section
When the ToR asks for a dedicated change management plan, generate a document covering:
- Change management approach and framework
- Organisational readiness assessment methodology (see
references/hard-and-soft-integration.mdsection 9) - Stakeholder readiness assessment and change saturation analysis
- Communication plan (see
references/hard-and-soft-integration.mdsection 5) - Training and capability development plan (reference
capacity-building/SKILL.mdandreferences/hard-and-soft-integration.mdsection 6) - Change champion or change agent network design (see
references/lean-and-adaptive-change.mdsection 3) - Resistance management strategy (see
references/hard-and-soft-integration.mdsection 7) - Adoption measurement framework (see
references/lean-and-adaptive-change.mdsection 6) - Change sustainability and reinforcement plan
Follow east-african-english standards throughout.
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.

