Guide · Agent skill
How to use the Change Management Playbook agent skill
Updated · written with AI from the project's own documentation and checked against our catalogue data
The Change Management Playbook is an agent skill that gives your AI agent a structured framework for rolling out organizational changes such as reorgs, tool switches, strategy pivots, product shutdowns and culture changes. It is aimed at founders, leaders and managers who want a clear plan instead of an improvised announcement. After this guide you will know what the skill does, how to install it, how to ask for it in plain language and what to expect from its output.
Change Management Playbookalirezarezvani/claude-skills · MIT Download the skill Quick start
- 1Download the ZIP. Download the change-management skill ZIP from the skill's page in this directory.
- 2Unzip into a skills folder. Unzip the file into ~/.claude/skills/ for personal use, or into a project's .claude/skills/ folder.
- 3Or upload in the Claude apps. If you use the Claude apps, upload the ZIP under Settings → Capabilities → Skills.
- 4Ask in plain language. Describe your change, such as a reorg, tool switch or product shutdown, and mention change management or the rollout.
- 5Use the output as a plan. Adapt the timeline and communication sequence to your team, then check the legal or HR points with a professional where needed.
What the Change Management Playbook skill makes the agent do
When the skill is installed, the agent answers change-management questions using a structured playbook built on the ADKAR model (Awareness, Desire, Knowledge, Ability, Reinforcement), adapted for startups. The source describes this as a startup-speed adaptation of a model originally developed by Prosci for enterprises.
The playbook covers process changes, org restructures, strategy pivots and culture changes. For each type it suggests a rollout timeline and a communication sequence, and it offers guidance on handling resistance and change fatigue.
The skill is a thinking framework for planning. It does not change anything in your systems.
How to install the skill
You can install the skill in one of two ways. Download the ZIP from the skill's page in this directory, then either unzip it into your personal skills folder at ~/.claude/skills/ or into a project's .claude/skills/ folder.
If you use the Claude apps instead, upload the ZIP there under Settings → Capabilities → Skills.
- Personal install: unzip into ~/.claude/skills/ so it is available across your projects.
- Project install: unzip into the .claude/skills/ folder of a specific project.
- Claude apps: upload the ZIP under Settings → Capabilities → Skills.
How to trigger the skill with natural requests
You do not need a special command. The skill's description lists the situations it is meant for: announcing a reorg, switching tools, pivoting strategy, killing a product, changing leadership, or any request that mentions change management, change rollout, managing resistance, org change, reorg or pivot communication.
Describe your situation in plain words and say what you need, such as a communication sequence, a timeline or help with a difficult conversation.
- Help me plan the rollout for moving our whole team from Jira to Linear.
- We are merging two teams next month. What should the communication sequence look like?
- We are killing our second product. How should I announce it to the team?
- Some engineers are resisting the new deploy process. How do I handle the resistance?
What the playbook gives you for each type of change
The playbook gives each change type a timeline, the phase that is usually hardest, the reinforcement that matters most and a communication sequence. Process changes such as new tools or workflows are given a 4 to 8 week adoption window, with the hardest phase at Ability. Org changes are given 3 to 6 months to stabilize, with Desire as the hardest phase. Strategy pivots are given 3 to 12 months, and Awareness is usually hardest because people often doubt the pivot is real.
The skill also covers what to say when a leader is leaving or being replaced. The guidance is to be honest about what you can share and never to say only that the reasons cannot be shared.
- Process change: announce the why and go-live date two weeks ahead, then check adoption at week 2 and deprecate the old system at week 8.
- Org change: announce on Day 0, hold 1:1s on Day 1, publish an FAQ in week 1 and run a first retrospective in month 2.
- Strategy pivot: tell employees internally first, then reallocate resources within 2 weeks so the money visibly moves.
What the skill needs, and safety notes
The source lists no requirements. It does not run scripts and does not use the network, so it works only from the instructions in its files (SKILL.md and references/change-playbook.md).
The playbook gives general advice. It does not account for local law or your contracts, so it is not a substitute for professional advice. Treat any legal, HR or employment decision as one to check with a qualified professional.
- Requires: nothing listed in the source.
- Runs scripts: no.
- Uses network: no.
- Licence: MIT.
Tips for getting better output
Give the agent real context: team size, the actual reason for the change and the date you want to go live. The playbook is most useful when it can tailor the 'why' to your situation rather than produce a generic announcement.
Ask for the deeper reference too. The skill includes a reference document with startup examples, including a tool migration announcement, so you can request examples of how to word a message.
- State the honest reason for the change. The playbook stresses that vague announcements create work.
- Ask for one communication sequence at a time, such as the announcement, then the FAQ.
- Use it to draft, then edit the wording yourself so it sounds like you.
What people use it for
- Planning a reorg with a Day 0 announcement, Day 1 one-to-ones and a week 1 FAQ.
- Rolling out a new tool with a go-live date, training sessions and a week 2 adoption check-in.
- Drafting a strategy pivot announcement that tells employees internally before any external message.
- Preparing for resistance from a team by addressing fears directly and running a concerns session within 48 hours.
- Planning how to tell a team that a product is being shut down, with a clear reason and a consistent sequence.
Frequently asked questions
Is the Change Management Playbook skill free?
The source lists the licence as MIT. The source does not mention prices, so check the listing on this directory for any cost details.
What do I need to run the change-management skill?
The source lists no requirements. The skill does not run scripts and does not use the network, so it works from its instruction files alone.
How do I install the change-management skill?
Download the ZIP from this directory and unzip it into ~/.claude/skills/ or a project's .claude/skills/ folder. In the Claude apps, you can upload the ZIP under Settings → Capabilities → Skills.
Is this the same as Prosci ADKAR certification?
No. The source says ADKAR is a Prosci model and that this playbook is a startup-speed adaptation. It is not the full Prosci-certified methodology, which the source says large enterprises may need.
Can the skill replace HR or legal advice?
No. The playbook gives general advice and does not account for local law or your contracts. Check legal, HR and employment decisions with a qualified professional.
Does the skill change anything in my tools or systems?
No. The source describes it as a thinking framework for planning, not software that changes anything in your systems.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
This skill suits founders, leaders and managers who are planning a reorg, tool switch or product shutdown and want a structured timeline and communication sequence. It is less suitable for large enterprises that need full Prosci-certified methodology, or for anyone who needs legal, HR or employment decisions, since it gives general advice only.
Download the skill