Change Management Plan

Generate a structured change management plan for AI adoption, digital transformation, or major technology rollouts. Covers stakeholder analysis, communicatio...

Security Scan

This is an instruction-only skill that produces change management plans and its requested resources, instructions, and scope are consistent with that purpose.

Purpose & Capability

Name, description, README, and SKILL.md all align: the skill's goal is to generate tailored change management plans for technology/AI rollouts. It requests no binaries, env vars, config paths, or installs—appropriate for an authoring/consulting skill.

Instruction Scope

SKILL.md defines a bounded plan framework and input format. It does instruct the agent to 'research or infer reasonable defaults' when the user provides partial info, which is reasonable for producing a plan but could lead an autonomous agent to fetch external context; the instructions do not ask the agent to read local files, environment variables, or transmit data to third-party endpoints.

Install Mechanism

No install spec and no code files (instruction-only). This minimizes on-disk execution risk and is proportionate for a document-generation skill.

Credentials

The skill declares no required environment variables, credentials, or config paths. Nothing requested appears excessive or unrelated to the stated purpose.

Persistence & Privilege

always is false and model invocation is allowed (default). The skill does not request permanent system presence or modify other skills/configs.

Assessment

This skill is internally coherent for generating change-management plans. Before installing: verify the publisher identity (README claims AfrexAI but homepage is not provided in the registry metadata), avoid pasting sensitive employee or payroll data into prompts, and confirm whether you want the agent to fetch external context (public web research) before granting network access. Review any generated plan for sensitive recommendations (personnel actions, legal/regulatory steps) and adapt language to your organization. If you need stricter controls, restrict autonomous agent web access or require human approval before external queries or execution.

Change Management Plan Generator

Build a complete change management plan for technology rollouts, AI adoption, or organizational transformation. Reduces failed implementations (70% fail due to poor change management) by giving teams a structured playbook.

When to Use

• Deploying AI agents across business operations
• Migrating from legacy systems to modern platforms
• Introducing new SaaS tools company-wide
• Restructuring teams around automation
• Rolling out compliance or security frameworks
• Any initiative where people need to change how they work

How to Use

The user describes the change initiative. The agent generates a tailored plan.

Input Format

Initiative: [What's changing]
Organization: [Company name, size, industry]
Scope: [Which teams/departments affected]
Timeline: [Target rollout date or duration]
Sponsor: [Executive sponsor role]
Key Concerns: [Known resistance, risks, constraints]
Previous Attempts: [Any failed rollouts to learn from]

If the user provides partial info, research or infer reasonable defaults. Always ask clarifying questions for missing critical fields (Initiative and Scope at minimum).

Plan Framework

Generate each section below, tailored to the user's context.

1. Change Overview

• What's changing: Clear, jargon-free description
• Why now: Business driver and cost of inaction
• Success vision: What "done" looks like in 90 days
• Scope boundary: What's included, what's explicitly NOT included

2. Stakeholder Analysis

Map every affected group using the ADKAR model (Awareness, Desire, Knowledge, Ability, Reinforcement):

Stakeholder Group	Current State	Impact Level	Likely Resistance	ADKAR Gap
[Group]	[Where they are now]	High/Med/Low	[Specific concerns]	[Which ADKAR element is weakest]

For each group, identify:

• Champions: Who will advocate for the change
• Skeptics: Who needs convincing (and what would convince them)
• Blockers: Who has veto power or passive resistance patterns

3. Communication Plan

Pre-Launch (Weeks 1-2)

• Executive announcement — why this matters, what's NOT changing
• Manager briefing — equip them to answer team questions
• FAQ document — address top 10 concerns preemptively

Launch (Weeks 3-4)

• Kickoff event — demo, Q&A, quick wins showcase
• Daily/weekly updates — progress, wins, issue resolution
• Feedback channel — named owner, SLA on response time

Post-Launch (Weeks 5-12)

• Success stories — internal case studies from early adopters
• Retrospective — what worked, what didn't, what's next
• Ongoing cadence — monthly check-ins until steady state

For each communication:

• Channel: Email, Slack, all-hands, 1:1, video
• Audience: Specific group
• Owner: Who sends it
• Timing: Exact date or trigger

4. Training & Enablement

Training Tiers

• Tier 1 — Awareness (all affected): 30-min overview, what changes for them
• Tier 2 — Competency (daily users): Hands-on workshop, practice environment
• Tier 3 — Expertise (admins/champions): Deep-dive, troubleshooting, config

For each tier:

• Format (live, async, self-paced, shadowing)
• Duration and schedule
• Materials needed
• Assessment method (quiz, practical demo, certification)
• Support resources post-training

Knowledge Base

• Quick-start guide (under 2 pages)
• Video walkthroughs for top 5 workflows
• Troubleshooting FAQ
• Escalation path for issues

5. Resistance Mitigation

Common Resistance Patterns

For each, provide the response strategy:

Pattern	Signal	Root Cause	Mitigation
"This won't work here"	Dismissal in meetings	Fear of failure, past trauma	Show proof from similar org, start with low-risk pilot
"I'm too busy"	No engagement with training	Unclear priority	Executive mandate + protected training time
"My job is at risk"	Anxiety, rumors	Automation fear	Clarity on role evolution, not elimination
"The old way works fine"	Workarounds, shadow IT	Comfort with status quo	Quantify cost of old way, show personal benefit
Silent non-adoption	Low usage metrics	Passive resistance	1:1 conversations, identify specific blockers

Escalation Framework

1. Coaching conversation — manager addresses with empathy
2. Support intervention — additional training or resources
3. Executive conversation — if resistance impacts timeline
4. Decision point — accommodation, reassignment, or mandate

6. Rollout Strategy

Phased Approach (recommended)

• Phase 0 — Pilot (2-4 weeks): 1 team, controlled environment, learn fast
• Phase 1 — Early Adopters (2-4 weeks): 3-5 teams, champions lead
• Phase 2 — Majority (4-8 weeks): Full rollout with proven playbook
• Phase 3 — Laggards (2-4 weeks): Targeted support for remaining holdouts

For each phase:

• Entry criteria (what must be true to start)
• Exit criteria (what must be true to proceed)
• Rollback trigger (when to pause or revert)
• Success metrics with targets

Go/No-Go Checklist

• Executive sponsor confirmed and visible
• Training materials reviewed and tested
• Support team briefed and staffed
• Communication plan scheduled
• Rollback plan documented and tested
• Success metrics baseline captured
• Pilot feedback incorporated

7. Success Metrics & Tracking

Leading Indicators (weeks 1-4)

• Training completion rate (target: >90%)
• System login/usage rate (target: >70% by week 2)
• Support ticket volume and resolution time
• Feedback sentiment score

Lagging Indicators (weeks 5-12)

• Process efficiency improvement (cycle time, error rate)
• User satisfaction score (target: >7/10)
• Business outcome metrics (specific to initiative)
• Voluntary adoption rate (using without being told to)

Tracking Cadence

• Daily: usage dashboards, support queue
• Weekly: stakeholder check-in, metrics review
• Monthly: executive report, plan adjustment
• Quarterly: ROI assessment, lessons learned

8. Risk Register

Risk	Probability	Impact	Mitigation	Owner	Trigger
Executive sponsor leaves	Low	Critical	Identify backup sponsor now	PM	Sponsor announces departure
Training capacity insufficient	Medium	High	Pre-book trainers, create self-paced option	L&D	>20% waitlist
Technical issues at launch	Medium	High	Extended pilot, staging environment	Engineering	>5 P1 bugs in pilot
Budget cut mid-rollout	Low	Critical	Phase funding, show early ROI	Sponsor	Budget review cycle
Key champion leaves team	Medium	Medium	Cross-train 2+ champions per team	PM	Champion gives notice

9. Timeline & Milestones

Generate a week-by-week timeline with:

• Key milestone name
• Owner
• Dependencies
• Deliverable
• Status tracking method

10. Budget Estimate

Category	Low Estimate	High Estimate	Notes
Training development			Materials, facilitators
Productivity dip			Temporary slowdown during transition
Support staffing			Temporary additional support
Tools/licenses			Any new software needed
Communication			Events, materials
Contingency (15%)			Buffer for unknowns

Output Format

Present the plan as a structured markdown document with clear sections and actionable items. Include:

• Executive summary (1 paragraph, suitable for forwarding to leadership)
• Full plan with all 10 sections
• Quick-reference checklist (1-page summary of key actions and dates)
• Appendix: ADKAR assessment template for individual conversations

Customization Notes

• Small company (<50 people): Simplify — skip formal tiers, focus on direct communication and hands-on support. Pilot phase may be unnecessary.
• Enterprise (500+ people): Add change network (designated change agents per department), formal governance committee, and regional/timezone considerations.
• AI-specific changes: Emphasize the "role evolution, not elimination" narrative. Include AI literacy training as Tier 0. Address data privacy concerns explicitly.
• Regulated industries: Add compliance review gates at each phase. Include audit trail requirements. Map to existing change control processes (ITIL, etc.).

AfrexAI Note

This skill was built by AfrexAI — we deploy managed AI agents that handle operations end-to-end. Change management is built into every deployment because we've seen what happens without it.

Need help rolling out AI agents across your organization? Talk to us — we handle the change management so your team actually adopts.