change-request
Create a change management request with impact analysis and rollback plan. Use when proposing a system or process change that needs approval, preparing a change record for CAB review, documenting risk and rollback steps before a deployment, or planning stakeholder communications for a rollout.
Security Assessment
About change-request
Change Request produces a structured change management document for a proposed system or process change, complete with impact analysis, risk assessment, and a rollback plan. Invoked as a slash command with a short change description, it is aimed at moments when a change needs formal approval: preparing a record for Change Advisory Board (CAB) review, documenting risk and reversal steps before a deployment, or planning the stakeholder communications that accompany a rollout.
The request is built around an assess-plan-execute-sustain framework. The assess step clarifies what is changing, who is affected, how significant it is, and what resistance to expect. Planning covers communication, training, support, and a milestone timeline. Execution focuses on announcing the why, training and supporting users, monitoring adoption, and addressing resistance, while the sustain step measures adoption, reinforces new behaviors, and captures lessons learned. Underlying communication principles stress explaining the why before the what, communicating early and often across multiple channels, and acknowledging what is being lost rather than only what is gained.
The output is a ready-to-fill Markdown template with clearly delineated sections: a header with requester, date, priority, and status; description and business justification; an impact analysis table spanning users, systems, processes, and cost; a risk assessment table pairing likelihood and impact with mitigations; an implementation plan; a communication plan; a rollback plan with trigger, steps, and verification; and a table of required approvals. When connectors are available the skill can extend beyond drafting: an ITSM integration can create the change ticket and pull the CAB schedule and approval workflows, a project tracker can link implementation tasks and dependencies, and a chat integration can draft stakeholder notifications and post updates. Practical tips reinforce being specific about impact (naming the 200 affected billing users rather than everyone), always preparing a rollback plan even when confident, and communicating early to build buy-in instead of triggering surprise-driven resistance.
FAQ
When should I use this skill?
When proposing a system or process change that needs approval, for example preparing a change record for CAB review, documenting risk and rollback before a deployment, or planning rollout communications.
What framework does it follow?
The assess-plan-execute-sustain change management framework, covering what is changing and who is affected, communication/training/support planning, execution and adoption monitoring, and sustaining the change afterward.
What sections does the generated change request include?
A header (requester, date, priority, status), description, business justification, impact analysis and risk assessment tables, an implementation plan, a communication plan, a rollback plan with trigger/steps/verification, and required approvals.
Can it create tickets automatically?
Only if connectors are available. With an ITSM connector it can create the change request ticket and pull the change advisory board schedule and approval workflows; a project tracker can link tasks and a chat connector can draft notifications.
Does it help with the rollback plan?
Yes. The template includes a dedicated rollback section specifying the trigger for rolling back, the step-by-step reversal, and how to verify the rollback worked, and the tips stress always having one.
Install change-request
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
anthropics/knowledge-work-plugins