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.
Documentation
/change-request
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Create a structured change request with impact analysis, risk assessment, and rollback plan.
Usage
/change-request $ARGUMENTS
Change Management Framework
Apply the assess-plan-execute-sustain framework when building the request:
1. Assess
What is changing?
Who is affected?
How significant is the change? (Low / Medium / High)
What resistance should we expect?
2. Plan
Communication plan (who, what, when, how)
Training plan (what skills are needed, how to deliver)
Support plan (help desk, champions, FAQs)
Timeline with milestones
3. Execute
Announce and explain the "why"
Train and support
Monitor adoption
Address resistance
4. Sustain
Measure adoption and effectiveness
Reinforce new behaviors
Address lingering issues
Document lessons learned
Communication Principles
Explain the why before the what
Communicate early and often
Use multiple channels
Acknowledge what's being lost, not just what's being gained
Provide a clear path for questions and concerns
Output
## Change Request: [Title]**Requester:** [Name] |
If Connectors Available
If ~~ITSM is connected:
Create the change request ticket automatically
Pull change advisory board schedule and approval workflows
If ~~project tracker is connected:
Link to related implementation tasks and dependencies
Track change progress against milestones
If ~~chat is connected:
Draft stakeholder notifications for the communication plan
Post change updates to the relevant team channels
Tips
Be specific about impact — "Everyone" is not an impact assessment. "200 users in the billing team" is.
Always have a rollback plan — Even if you're confident, plan for failure.
Communicate early — Surprises create resistance. Previews create buy-in.~~