change-management

Overview of change-management skill

What change-management is built to do

The change-management skill is a C-level advisory playbook for planning and communicating organizational change without creating avoidable confusion, resistance, or fatigue. It adapts the ADKAR model for startup-speed environments, where leaders often need to announce a reorg, tool migration, process change, strategy pivot, product sunset, leadership transition, or culture shift before every detail is perfect.

Best-fit users and decisions

This change-management skill is most useful for founders, executives, chiefs of staff, people leaders, and operators who need a practical rollout plan rather than a generic “write an announcement” prompt. It helps when the real job is not only explaining the change, but also sequencing stakeholders, anticipating objections, creating awareness and desire, and deciding what reinforcement is needed after launch.

What makes it different from a generic prompt

The skill’s value is its structured change lens: it pushes the agent to separate the business reason, stakeholder incentives, capability gaps, rollout plan, resistance patterns, and fatigue risks. The included references/change-playbook.md adds concrete examples for tool migrations and reorgs, making the output more grounded than a single communication template.

When it may not be enough

Use the skill as an advisory and drafting framework, not as legal, HR compliance, or labor-relations guidance. For layoffs, regulated workforce changes, union contexts, compensation changes, or material employment risk, pair the output with counsel and internal HR review before sending anything.

How to Use change-management skill

change-management install and repository path

Install the skill from the GitHub repository with:

npx skills add alirezarezvani/claude-skills --skill change-management

The source lives at c-level-advisor/skills/change-management. After install, read SKILL.md first for the operating model, then open references/change-playbook.md for deeper examples and better prompt ingredients. There are no scripts or automation files; this is a reasoning, planning, and communication skill.

Inputs that produce the best output

Give the skill the change context before asking for deliverables. Strong inputs include:

• Type of change: reorg, process change, tool migration, pivot, leadership change, product shutdown
• Business reason: what problem is being solved and what happens if nothing changes
• Stakeholder groups: executives, managers, ICs, customers, partners, board, affected teams
• Current sentiment: trust level, prior failed changes, fatigue, likely objections
• Timeline: announcement date, transition period, training, decision deadlines
• Non-negotiables: what is decided, what is still open, what cannot be promised
• Desired artifacts: rollout plan, FAQ, manager talking points, announcement, risk map

A weak prompt is: “Help me announce a reorg.”
A stronger prompt is: “Use the change-management skill to plan a reorg announcement. We are moving Customer Success from Sales to Operations because retention work is being deprioritized under new-logo targets. Affected groups are Sales, CS, Ops, and existing enterprise customers. Trust is mixed because we changed reporting lines twice last year. Draft the ADKAR-based rollout plan, executive announcement, manager talking points, and resistance risks.”

Suggested workflow for change-management usage

Start with diagnosis before messaging. Ask the skill to identify the ADKAR gaps: do people understand why, want the change, know how to execute, have the ability and resources, and see reinforcement after launch? Then move into artifacts.

A practical workflow:

1. Ask for a stakeholder impact map.
2. Ask for the “why now” narrative and risks if no change is made.
3. Generate the rollout sequence by audience and timing.
4. Draft the announcement, manager FAQ, and objection responses.
5. Review for overpromising, ambiguity, and change fatigue.
6. Iterate with actual leadership constraints before publishing.

Files to read before relying on output

Read SKILL.md to understand the trigger cases, ADKAR structure, and change categories. Read references/change-playbook.md when you need stronger examples, especially for tool migrations and reorgs. The reference file is useful because it shows the difference between merely informing people and explaining the operational reason behind a change.

change-management skill FAQ

Is change-management for Change Management beginners?

Yes. The skill is approachable if you know the business context but do not know formal change frameworks. It explains the work through practical questions: why the change is happening, who is affected, what resistance will appear, and how adoption will be reinforced. Beginners should still provide concrete context rather than expect the skill to infer internal politics.

How is it different from asking for a communication plan?

A basic communication prompt usually produces a timeline and announcement. The change-management skill adds adoption logic: awareness, desire, knowledge, ability, and reinforcement. That matters because many rollouts fail after the announcement, when managers cannot answer questions, teams do not know what to do differently, or people quietly wait for the change to disappear.

What kinds of changes fit best?

Best fits include startup or scaleup changes with real operational impact: switching tools, restructuring teams, changing decision rights, pivoting strategy, killing a product, introducing new operating rituals, or changing leadership expectations. It is especially useful when stakeholders may agree with the business logic but resist the disruption.

When should I not use this skill alone?

Do not use it alone for legally sensitive employment actions, crisis communications, public company disclosures, regulated customer notices, or changes that require formal consultation. It can help prepare questions, messaging drafts, and stakeholder maps, but the final plan should go through qualified internal review.

How to Improve change-management skill

Improve change-management results with sharper context

The most important upgrade is specificity. Replace “people may resist” with the actual resistance pattern: loss of autonomy, fear of layoffs, skepticism from prior failed tools, manager overload, customer disruption, or unclear incentives. The more precisely you name the resistance, the more useful the skill’s rollout plan and talking points become.

Ask for tradeoffs, not just templates

For high-stakes change-management usage, request options. For example: “Give me a fast rollout, a trust-preserving rollout, and a minimum-disruption rollout, with risks for each.” This helps leaders see the cost of speed, transparency, and participation instead of receiving one polished but untested plan.

Iterate after the first draft

After the first output, feed back what feels unrealistic: “This assumes managers have time for training; they do not,” or “The announcement is too executive-centered; employees care about role impact.” Then ask the skill to revise the plan by stakeholder group. This produces better outputs than asking for one final memo immediately.

Watch for common failure modes

The main failure modes are vague business rationale, excessive positivity, underestimating fatigue, and treating communication as the whole change. Ask the skill to run a final critique: “Identify where this plan may sound evasive, where stakeholders may not believe us, and what reinforcement is missing 30 and 60 days after launch.”