Agent skill

Change Management Plan

by mohitagw15856 in mohitagw15856/pm-claude-skills

Create a structured change management plan for any organisational change.

MITAuto-check passed

Install Change Management Plan

skills CLI
$ npx skills add mohitagw15856/pm-claude-skills --skill change-management-plan -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mohitagw15856/pm-claude-skills change-management-plan --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/change-management-plan .claude/skills/change-management-plan && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
change-management-plan
GitHub stars
1.4k
Token cost
~1.5k tokens
SKILL.md length
718 words
Files
1
Skills in repo
1,348
Repo updated
First seen
Licence
MIT

At a glance

Create a structured change management plan for any organisational change.

  • Works in 7 steps: Change Summary → Stakeholder Analysis → Impact Assessment → …
  • Asked to write a change management plan
  • SKILL.md covers Required Inputs, Output Structure, 1. Change Summary and 2. Stakeholder Analysis, plus 8 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Change Management Plan is an agent skill from mohitagw15856/pm-claude-skills. 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.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.

When your agent uses it

  • Asked to write a change management plan
  • Manage a change initiative
  • Plan a system rollout
  • Lead an organisational transformation

Example prompts

  • “/change-management-plan”

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Change Summary
  2. Stakeholder Analysis
  3. Impact Assessment
  4. Communication Plan
  5. Training and Support Plan
  6. Resistance Management
  7. Adoption Metrics

What it can do on your machine

Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Change Management Plan loads about 1.5k tokens when it runs. Until then it costs about 89 tokens; SKILL.md has 718 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~89
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 718 words, ~1,515 tokens.

Download SKILL.mdSave it as .claude/skills/change-management-plan/SKILL.md (or your agent's skills folder).
name
change-management-plan
description
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.

Change Management Plan Skill

Produces a structured change management plan — because most change initiatives fail not because the change is wrong, but because people aren't brought along with it.

Required Inputs

Ask the user for these if not provided:

  • 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)

Output Structure


Change Management Plan: [Change Name]

Change sponsor: [Executive owner] Change manager: [Who is running this] Go-live date: [Date] Affected population: [N people, N teams/locations]


1. Change Summary

From (current state): [Specific description of today's situation] To (future state): [Specific description of what changes] Why this change is happening: [Honest explanation — people adopt change faster when they understand the real reason] What stays the same: [Explicitly naming what is NOT changing reduces anxiety]


2. Stakeholder Analysis

Stakeholder groupSizeImpact levelCurrent sentimentWhat they need
[Group][N]High/Med/LowSupportive / Neutral / Resistant[Specific concern or need]

Key influencers to engage early: [Name the informal leaders, respected voices, and early adopters who can help. And the resistors who need direct attention.]


3. Impact Assessment

AreaImpactSeverityAction needed
Daily workflow[What changes day-to-day]High/Med/Low[Training / support / redesign]
Systems or tools[What tools are affected]
Roles and responsibilities[Any role changes]
Processes[Process changes]
Metrics and targets[Any KPI changes]

4. Communication Plan

Core message: [The 1-sentence summary everyone should understand and remember]

AudienceMessage focusChannelTimingOwner
All staff[Why this is happening + what to expect]All-hands / Email[T-6 weeks]Sponsor
Managers[How to support their teams]Manager briefing[T-5 weeks]Change manager
Directly affected teams[What changes for them specifically]Team meeting[T-4 weeks]Line manager
[Other group][Tailored message]

Communication principles:

  • Over-communicate — people need to hear a message 7 times to internalise it
  • Use managers to cascade, not just top-down announcements
  • Create a feedback channel — questions left unanswered become rumours

5. Training and Support Plan

AudienceTraining typeTimingDurationDeliveryOwner
[Group][e.g. Hands-on system training][T-2 weeks][2 hours][In-person / online][Owner]

Go-live support:

  • [What support is available on day 1 — helpdesk, floor walkers, champions]
  • [Escalation path for issues in first 30 days]

6. Resistance Management

Anticipated resistance sources:

ConcernWho holds itRoot causeResponse
[e.g. "This will increase my workload"][Middle managers][Loss of autonomy][Specific action to address]

Resistance management principles:

  • Acknowledge concerns genuinely — dismissing resistance amplifies it
  • Involve resistors in design where possible — converts them into advocates
  • Distinguish between genuine concerns (worth addressing) and preference for the status quo (to be managed, not solved)

Show full SKILL.md (258 more words)Show less

7. Adoption Metrics

MetricBaselineTargetMeasurement pointOwner
[System usage rate][0%][80%][30 days post go-live][Owner]
[Process compliance][X%][Y%][60 days][Owner]
[Staff confidence score][Survey score][Target][90 days][Owner]

Adoption milestones:

  • D+7: [First check — early issues identified]
  • D+30: [First adoption review]
  • D+90: [Sustained adoption confirmed or remediation plan activated]

Quality Checks

  • "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")

Anti-Patterns

  • 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

Example Trigger Phrases

  • "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]?"

© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/change-management-plan of mohitagw15856/pm-claude-skills.

Open the folder on GitHubat commit 1cbf1f0

Compare with similar skills

Change Management Plan next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Change Management Plan compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Change Management Plan this skillmohitagw15856/pm-claude-skills1.4k—~1.5kAutomated safety check: PassMIT
Code Organisationjd-solanki/slidev-theme-dracula161—~1.6kAutomated safety check: PassNone
Screen Adverse Mediasickn33/agentic-awesome-skills47k1 repos~1.1kAutomated safety check: PassApache-2.0
Conventions Checkpolarsource/polar10k—~476Automated safety check: PassMIT
Backofficelatitude-dev/latitude-llm4.7k—~1.9kAutomated safety check: PassMIT
Design TokenOwl-Listener/designer-skills2.9k1 repos~387Automated safety check: PassMIT

Similar skills

  • Code Organisation

    jd-solanki/slidev-theme-dracula

    Decide where code lives — the directory tree, module and package boundaries, and the layout inside a file.

    161 GitHub stars~1.6k tokensUpdated 3 mo ago
    DevelopmentAuto-check passed
  • Screen Adverse Media

    sickn33/agentic-awesome-skills

    Screen a person or organisation for adverse media coverage, PEP status, and sanctions exposure — corroboration-gated, returns "review" never "guilty".

    47k GitHub starsUsed in 1 repo~1.1k tokens
    SecurityAuto-check passed
  • Conventions Check

    polarsource/polar

    Check a diff against Polar's written conventions in server/AGENTS.md and clients/AGENTS.md — module structure, repository and service patterns, session types, auth dependencies, test organisation…

    10k GitHub stars~476 tokensUpdated yesterday
    Data & AnalyticsAuto-check passed
  • Backoffice

    latitude-dev/latitude-llm

    Adding, modifying, or guarding staff-only /backoffice features — cross-organisation admin tools gated behind users.role === "admin".

    4.7k GitHub stars~1.9k tokensUpdated 2 days ago
    Auto-check passed
  • Design Token

    Owl-Listener/designer-skills

    Define and organise tokens for colour, spacing, type, and elevation with naming and usage rules.

    2.9k GitHub starsUsed in 1 repo~387 tokens
    Frontend & DesignAuto-check passed
  • Aussie Business English

    jezweb/claude-skills

    Australian business English for professional writing — warm, direct, EN-AU spelling (colour, organise, centre), no filler words.

    1.1k GitHub stars~680 tokensUpdated 2 days ago
    Writing & ContentAuto-check passed

More from mohitagw15856/pm-claude-skills

All 1,348 skills in this repo
  • Car Tco

    mohitagw15856/pm-claude-skills

    Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…

    1.4k GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed
  • Cs Health Scorecard

    mohitagw15856/pm-claude-skills

    Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.

    1.4k GitHub stars~2.4k tokensUpdated 2 days ago
    Auto-check passed
  • Exit Waterfall

    mohitagw15856/pm-claude-skills

    Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.

    1.4k GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed
  • Feature Prioritisation

    mohitagw15856/pm-claude-skills

    Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.

    1.4k GitHub stars~2k tokensUpdated 2 days ago
    Auto-check passed
  • Fire Number

    mohitagw15856/pm-claude-skills

    Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.

    1.4k GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed
  • Freelance Rate

    mohitagw15856/pm-claude-skills

    Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.

    1.4k GitHub stars~1.2k tokensUpdated 2 days ago
    Auto-check passed

Questions about Change Management Plan

What does Change Management Plan do?

Create a structured change management plan for any organisational change. Change Management Plan is an agent skill from mohitagw15856/pm-claude-skills. Create a structured change management plan for any organisational change.

When should I use Change Management Plan?

Change Management Plan fits situations like: asked to write a change management plan; manage a change initiative; plan a system rollout; lead an organisational transformation.

How do I install Change Management Plan in Claude Code?

Run `npx skills add mohitagw15856/pm-claude-skills --skill change-management-plan -a claude-code`. Or copy the skill folder (skills/change-management-plan in mohitagw15856/pm-claude-skills) into .claude/skills/change-management-plan in your project. Claude Code loads it when a task matches its description.

How do I install Change Management Plan in Codex?

Run `npx skills add mohitagw15856/pm-claude-skills --skill change-management-plan -a codex`. Or copy the skill folder (skills/change-management-plan in mohitagw15856/pm-claude-skills) into .agents/skills/change-management-plan in your project. Codex loads it when a task matches its description.

Can I use Change Management Plan in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill change-management-plan -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/change-management-plan, .gemini/skills/change-management-plan, .github/skills/change-management-plan and .opencode/skills/change-management-plan in your project.

What does Change Management Plan need to run?

SKILL.md names no scripts, command-line tools or credentials: Change Management Plan is instructions for the agent only.

Does Change Management Plan access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Change Management Plan safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Change Management Plan use?

Change Management Plan is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Change Management Plan use?

About 1.5k tokens (SKILL.md is roughly 6.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Change Management Plan?

Skills that share tags, products or a category with Change Management Plan: Code Organisation (jd-solanki/slidev-theme-dracula, 161 stars), Screen Adverse Media (sickn33/agentic-awesome-skills, 47k stars), Conventions Check (polarsource/polar, 10k stars) and Backoffice (latitude-dev/latitude-llm, 4.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Change Management Plan?

mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.

Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.