Change Request

1---2name: change-request3description: 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.4argument-hint: "<change description>"5---6 7# /change-request8 9> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md).10 11Create a structured change request with impact analysis, risk assessment, and rollback plan.12 13## Usage14 15```16/change-request $ARGUMENTS17```18 19## Change Management Framework20 21Apply the assess-plan-execute-sustain framework when building the request:22 23### 1. Assess24- What is changing?25- Who is affected?26- How significant is the change? (Low / Medium / High)27- What resistance should we expect?28 29### 2. Plan30- Communication plan (who, what, when, how)31- Training plan (what skills are needed, how to deliver)32- Support plan (help desk, champions, FAQs)33- Timeline with milestones34 35### 3. Execute36- Announce and explain the "why"37- Train and support38- Monitor adoption39- Address resistance40 41### 4. Sustain42- Measure adoption and effectiveness43- Reinforce new behaviors44- Address lingering issues45- Document lessons learned46 47## Communication Principles48 49- Explain the **why** before the **what**50- Communicate early and often51- Use multiple channels52- Acknowledge what's being lost, not just what's being gained53- Provide a clear path for questions and concerns54 55## Output56 57```markdown58## Change Request: [Title]59**Requester:** [Name] | **Date:** [Date] | **Priority:** [Critical/High/Medium/Low]60**Status:** Draft | Pending Approval | Approved | In Progress | Complete61 62### Description63[What is changing and why]64 65### Business Justification66[Why this change is needed — cost savings, compliance, efficiency, risk reduction]67 68### Impact Analysis69| Area | Impact | Details |70|------|--------|---------|71| Users | [High/Med/Low/None] | [Who is affected and how] |72| Systems | [High/Med/Low/None] | [What systems are affected] |73| Processes | [High/Med/Low/None] | [What workflows change] |74| Cost | [High/Med/Low/None] | [Budget impact] |75 76### Risk Assessment77| Risk | Likelihood | Impact | Mitigation |78|------|-----------|--------|------------|79| [Risk] | [H/M/L] | [H/M/L] | [How to mitigate] |80 81### Implementation Plan82| Step | Owner | Timeline | Dependencies |83|------|-------|----------|--------------|84| [Step] | [Person] | [Date] | [What it depends on] |85 86### Communication Plan87| Audience | Message | Channel | Timing |88|----------|---------|---------|--------|89| [Who] | [What to tell them] | [How] | [When] |90 91### Rollback Plan92[Step-by-step plan to reverse the change if needed]93- Trigger: [When to roll back]94- Steps: [How to roll back]95- Verification: [How to confirm rollback worked]96 97### Approvals Required98| Approver | Role | Status |99|----------|------|--------|100| [Name] | [Role] | Pending |101```102 103## If Connectors Available104 105If **~~ITSM** is connected:106- Create the change request ticket automatically107- Pull change advisory board schedule and approval workflows108 109If **~~project tracker** is connected:110- Link to related implementation tasks and dependencies111- Track change progress against milestones112 113If **~~chat** is connected:114- Draft stakeholder notifications for the communication plan115- Post change updates to the relevant team channels116 117## Tips118 1191. **Be specific about impact** — "Everyone" is not an impact assessment. "200 users in the billing team" is.1202. **Always have a rollback plan** — Even if you're confident, plan for failure.1213. **Communicate early** — Surprises create resistance. Previews create buy-in.