SkillAgentSearch skills...

change-management

Framework for rolling out organizational changes without chaos, using ADKAR adapted for startups

Install / Use

npx skills add borghei/Claude-Skills --skill change-management

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

89/100

Supported Platforms

Universal

Tags

Our assessment of change-management

change-management scores 89/100 on our quality scale, 1706th of 4,702 Development & Engineering skills we index (top 37%).

Its SKILL.md is 20 KB long, well organised into 49 sections with 6 code examples: a thorough specification that gives an agent plenty to work with.

It has 817 GitHub stars, a meaningful sign that others use it.

Substance
30/30
Structure
20/20
Description
12/15
Adoption
12/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so change-management is actively maintained.
  • Our last check on 2026-10-31 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-07. Automated pattern scan on 2026-10-07. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

change-management compared with similar skills

All 4 of these similar skills score higher than change-management; compare them before choosing.

SkillScoreStarsUpdatedFormat
change-management (this skill)by borghei8981757d agoSKILL.md
taste-skillby Leonxlnx100117.6k9d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.3ktodayCLAUDE.md
claude-howtoby luongnv8910047.4k3d agoCLAUDE.md
lobehubby lobehub10085.7ktodayMCP Server

Frequently asked questions

How do I install change-management?
Run npx skills add borghei/Claude-Skills --skill change-management. The install tabs above show the steps for each supported agent.
Which AI agents does change-management work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is change-management safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is change-management still maintained?
The repository was last updated about 2 months ago, so change-management is actively maintained.

name: change-management description: > Framework for rolling out organizational changes without chaos, using ADKAR adapted for startups. Use when announcing a reorg, switching tools, pivoting strategy, killing a product, or managing change resistance. license: MIT + Commons Clause metadata: version: 2.0.0 author: borghei category: c-level domain: change-management updated: 2026-03-09 frameworks: - adkar-startup - change-communication - resistance-management - change-fatigue - change-playbooks - adoption-measurement triggers: - change management - ADKAR - organizational change - reorg - restructure - process change - tool migration - strategy pivot - change resistance - change fatigue - change communication - stakeholder management - adoption - compliance - change rollout - transition - new process - announce change - manage resistance

Change Management Playbook

Most changes fail at implementation, not design. This skill provides the complete framework for rolling out organizational changes -- from process tweaks to full strategic pivots -- with minimal disruption and maximum adoption.

Keywords

change management, ADKAR, organizational change, reorg, process change, tool migration, strategy pivot, change resistance, change fatigue, change communication, stakeholder management, adoption, compliance, change rollout, transition


Clarify First

Before generating, confirm these inputs. If any is unknown or vague, ASK — do not assume:

  • [ ] The change type (process, org/reorg, strategy pivot, or culture) — selects the playbook, timeline, and which ADKAR phase is hardest
  • [ ] What is changing and the honest business WHY — the WHY anchors every communication; without it the rollout reads as arbitrary and breeds resistance
  • [ ] Who is affected and how (directly affected vs. broader org) — drives communication sequencing and the order in which audiences hear it
  • [ ] How many other changes are already active — if 3+ changes are running and under-absorbed, the plan must address change fatigue before adding more

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.


Change Type Selection

START: Change is needed
  |
  v
[What type of change?]
  |
  +-- Process Change (new tools, workflows)
  |     Timeline: 4-8 weeks
  |     Hardest phase: Ability
  |     See: Process Change Playbook
  |
  +-- Org Change (reorg, new leader, team restructure)
  |     Timeline: 3-6 months
  |     Hardest phase: Desire
  |     See: Org Change Playbook
  |
  +-- Strategy Pivot (new direction, killed products)
  |     Timeline: 3-12 months
  |     Hardest phase: Awareness
  |     See: Strategy Pivot Playbook
  |
  +-- Culture Change (values refresh, behavior expectations)
        Timeline: 12-24 months
        Hardest phase: Reinforcement
        See: Culture Change Playbook

Core Model: ADKAR (Startup-Adapted)

Overview

| Phase | What It Is | Failure Symptom | |-------|-----------|----------------| | Awareness | People understand WHY the change is happening | "Nobody told me why" | | Desire | People want to participate (or at least don't resist) | "I understand but I don't agree" | | Knowledge | People know HOW to do things the new way | "I want to but I don't know how" | | Ability | People have time, tools, and support to change | "I know how but I can't do it yet" | | Reinforcement | The change sticks as the new default | "We tried but went back to the old way" |

ADKAR Diagnostic

When a change is struggling, identify which phase is broken:

| Symptom | Broken Phase | Fix | |---------|-------------|-----| | "Why are we doing this?" | Awareness | Re-communicate the WHY with data | | "This is a bad idea" | Desire | Address concerns, involve in HOW | | "I don't know how to do this" | Knowledge | Training, documentation, office hours | | "I keep reverting to old habits" | Ability | Practice time, reduce workload, support | | "We started but stopped" | Reinforcement | Measurement, recognition, remove old way |

ADKAR Implementation Timeline

| Week | Phase | Key Activities | |------|-------|---------------| | -4 | Awareness prep | Identify stakeholders, draft communication | | -2 | Awareness launch | CEO/leader video explaining WHY | | -1 | Desire building | Concerns session, address fears, involve in HOW | | 0 | Knowledge + Go-live | Training, documentation, launch | | 1-2 | Ability support | Office hours, help desk, reduced load | | 3-4 | Ability + early Reinforcement | Adoption check, public wins, feedback | | 6-8 | Full Reinforcement | Old way deprecated, adoption measured, recognized |


Resistance Patterns and Responses

Resistance Diagnostic Matrix

| Pattern | What They Say | What It Signals | Response | |---------|-------------|-----------------|---------| | Vocal opposition | "This won't work" | Awareness or credibility gap | Present evidence, acknowledge concern | | Timing challenge | "Why now?" | Awareness gap | Explain urgency and cost of delay | | Process complaint | "I wasn't consulted" | Desire gap | Acknowledge, involve in the HOW now | | Capacity excuse | "I don't have time" | Ability gap | Reduce load or extend timeline | | Historical reference | "We tried this before" | Trust gap | Name what is different this time | | Silent non-compliance | [No verbal pushback, just doesn't change] | Could be any phase | 1:1 conversation to diagnose | | Malicious compliance | [Does it technically but undermines] | Deep desire gap | Direct conversation about real concern |

Resistance Response Decision Tree

START: Resistance detected
  |
  v
[Is it vocal or silent?]
  |
  +-- VOCAL --> Good. They care enough to push back.
  |              |
  |              v
  |            [Is the concern valid?]
  |              |
  |              +-- YES --> Modify the change. Resistance is information.
  |              +-- NO  --> Address with data and empathy. Do not dismiss.
  |
  +-- SILENT --> Dangerous. Could be any ADKAR phase.
                 |
                 v
               [1:1 conversation with specific questions]
                 "What concerns you about this change?"
                 "What would need to be true for this to work for you?"
                 "What support would help?"

The Worst Response to Resistance

"Some people are just resistant to change."

This treats resistance as a personality flaw rather than a signal. Every resistance pattern is information about which ADKAR phase is broken. Diagnose before responding.


Change Communication Framework

Communication Sequencing

| Audience | Order | Channel | Content | |----------|-------|---------|---------| | Leadership team | 1st | In-person/video meeting | Full context + their role in rollout | | Directly affected employees | 2nd | Manager 1:1 or small group | Personal impact + support available | | All employees | 3rd | All-hands or written + Q&A | WHY + WHAT + timeline + FAQ | | External stakeholders | 4th (if applicable) | Appropriate channel | Need-to-know only |

Communication Template (CEO/Leader Announcement)

Structure:
  1. What is changing (1-2 sentences, direct)
  2. Why it is changing (the business reason -- honest)
  3. What this means for you (practical impact)
  4. What is NOT changing (stability anchor)
  5. Timeline (specific dates)
  6. How to ask questions (channel, person, office hours)
  7. What happens next (first concrete step)

Communication Cadence by Change Type

| Change Type | Pre-announcement | Launch Day | Week 1 | Month 1 | Month 3 | |-------------|-----------------|-----------|--------|---------|---------| | Process | Heads-up to leads | All-hands email | FAQ published | Adoption check | Old way removed | | Org | 1:1s with affected | Synchronous meeting | FAQ + manager 1:1s | Retro | Health check | | Strategy | Leadership alignment | All-hands with Q&A | Team-level "what does this mean" | Resource proof | First milestone | | Culture | Input gathering | Story-based announcement | Behavior anchors | Reviews reflect it | Ongoing |


Change Fatigue

Fatigue Detection

| Signal | Severity | Response | |--------|----------|----------| | Eye-rolls during announcements | Early | Acknowledge the pace, show results of previous changes | | Low attendance at change sessions | Moderate | Make attendance optional but results visible | | Fast paper compliance, slow real adoption | Significant | Pause non-critical changes | | "Here we go again" comments | Significant | Audit change inventory, communicate stability | | Complete disengagement | Critical | Freeze changes, rebuild trust |

Fatigue Prevention Rules

| Rule | Implementation | |------|---------------| | Finish what you start | Do not launch new change while previous is absorbing | | One major change at a time | Space 2-3 months between significant changes | | Announce stability | Explicitly state what is NOT changing | | Show results | Publish what previous change achieved before launching next | | Change budget | Treat organizational attention as a finite resource |

Change Inventory

Before launching any new change, inventory all active changes:

| Change | Phase | Start Date | Absorption % | Can It Pause? | |--------|-------|-----------|-------------|---------------| | New CRM rollout | Ability | 2 weeks ago | 60% | No | | Engineering reorg | Desire | 1 month ago | 40% | Yes | | Values refresh | Reinforcement | 3 months ago | 75% | No |

Rule: If 3+ changes are active and < 70% absorbed, do not add another.


Playbook 1: Process Change

Timeline: 4-8 weeks | Hardest Phase: Ability

| Week | Activity | Owner | |------|----------|-------| | -2 | Announce WHY + go-live date | Change sponsor | | -1 | Training sessions available | Change team | | 0 | Go-live + support person available | Change team | | 2 | Adoption check: who is using it, who is not | Change team | | 4 | Feedback collection + public wins | Change sponsor | | 8 | Old system deprecated | IT + Change team |


Playbook 2: Org Change

Timeline: 3-6 months | Hardest Phase: Desire

| Timing | Activity | Owner | |--------|----------|-------| | Day 0 | Announce with WHY -- synchronous, in-person preferred | CEO/leader | | Day 1 | 1:1s with most affected by their manager | Managers | | Week 1 | FAQ published with honest answers | HR + Change team | | Week 2-4 | New structure operating (do not delay) | All leaders | | Month 2 | First retrospective | Change team | | Month 3-6 | Regular health check-ins | HR |

What to say about a leader departure: Be honest about what you can share. Never say "we can't share the reasons" without offering what you CAN say about what it means for the team.


Playbook 3: Strategy Pivot

Timeline: 3-12 months | Hardest Phase: Awareness

| Timing | Activity | Owner | |--------|----------|-------| | Pre-announcement | Leadership alignment (everyone must be on same page) | CEO | | Day 0 | Internal announcement first (employees BEFORE press) | CEO | | Week 1 | Team-level "what does this mean for us" conversations | Team leads | | Week 2 | Resource reallocation announced | CFO + COO | | Month 1 | First milestone of new direction visible | Relevant leader | | Ongoing | Regular updates on new direction progress | CEO |

What kills pivots: Announcing a new direction while still funding the old one at the same level. Move the resources or the pivot is not real.


Playbook 4: Culture Change

Timeline: 12-24 months | Hardest Phase: Reinforcement

| Phase | Activity | Timeline | |-------|----------|----------| | Input | Involve representative sample in defining the change | Month 1-2 | | Announce | Story-based announcement with observed

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars817
CategoryDevelopment
Updated1mo ago
Forks141

Languages

HTML

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium