CM
Change Management Plan
🔵 Stable🕐 updated 2026-06-08
🔷 SkillSpec L3
pm-hr
Create a structured change management plan for any organisational change. Use when asked to write a change management plan, manage a change initiative, plan a system rollout, or lead an organisational transformation. Produces a plan covering stakeholder analysis, impact assessment, communication strategy, and resistance management.
📚 Based on Kotter's 8 steps; ADKAR (Prosci)
🗣 Say this to your agent
“Write a change management plan for [initiative]”“Help me plan the rollout of [system change] for [team/org]”“Create a communication and training plan for [change]”“How do I manage resistance to [change]?”
What to give it
▸The change — what is changing, and what is the current state?
▸Scale — how many people affected, in how many teams/locations?
▸Timeline — when does the change go live? How long is the transition?
▸Sponsor — who is accountable at senior level?
▸Key concern — what is the biggest risk to adoption?
▸What happens if change fails — consequences of low adoption
✅ The bar it holds itself to
Every skill in this library self-verifies — these are this skill's own quality checks, straight from its definition.
✓"What stays the same" is explicitly addressed
✓Stakeholder analysis includes resistors, not just supporters
✓Communication plan uses managers to cascade (not just top-down)
✓Training is timed before go-live (not after)
✓Adoption metrics have a measurement date and owner
✓Resistance management has specific responses (not just "communicate more")
⚠️ What it refuses to do
Do not treat communication as a one-time announcement — people need to hear a message multiple times before they internalise it; plan for repeated touchpoints
Do not assign change management to a single owner without involving line managers — managers are the most effective cascade channel and must be briefed before their teams
Do not schedule training after go-live — people who learn a new system on the day they need to use it will revert to the old process
Do not ignore resistors in the stakeholder analysis — resistors who are not explicitly engaged will undermine adoption, especially informal leaders
Do not measure adoption only at go-live — the real test is sustained adoption at 90 days, when novelty has worn off
Install
npx pm-claude-skills add --agent claude # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y pm-claude-skills-mcp
Start with
Related skills
🔌 Embed this skill
Drop this on your blog, docs, or site — it renders a "Run this skill" card:
<div data-pm-skill="change-management-plan"></div>
<script src="https://mohitagw15856.github.io/pm-claude-skills/embed.js" async></script>
💬 Discussion
Change Management Plan is one of 1098 open-source professional AI agent skills — all SkillSpec L3.
Try them all in the browser · ⭐ Star on GitHub · Browse the full catalog