Skill Tracer
Skills › Knowledge Work Plugins › change-request

change-request

skill · 121 lines · Apache-2.0 · operations/skills/change-request/SKILL.md

The facts

Its description

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.

The description the agent reads to decide when to use it.

From its settingsline 3

When it starts

The agent picks this when someone wants a formal change request written up — a system or process change that needs approval, a change record for CAB review, or a deployment that needs documented risk and rollback steps. The description is about producing the structured request document itself, not about doing the change.

Things a person might say (the model's guesses)

  • “I need a change request for moving our billing system to the new platform”
  • “Write up a change record for CAB review before we deploy the new auth service”
  • “Draft a change request with impact analysis and a rollback plan for switching CRMs”

A model's summary of when it is used.

A model's reading

What it takes when started

<change description>

What to type after its name when you start it.

From its settingsline 4

Licence

Apache-2.0, from LICENSE

The terms its author shares it under, which let it be shown here.

From the repositorylicence text

The text

Open on GitHub

Most marks come from matching words in the file, so treat them as pointers.

1---
2name: change-request
3description: 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-request
8
9> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md).
11Create a structured change request with impact analysis, risk assessment, and rollback plan.

/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.

Raw lines 1 to 12
Boilerplate, lines 13 to 18. The same text appears in 24 other files here. Close
13## Usage
15```
16/change-request $ARGUMENTS
17```
19## Change Management Framework
21Apply the assess-plan-execute-sustain framework when building the request:

Change Management Framework

Apply the assess-plan-execute-sustain framework when building the request:

Raw lines 19 to 22
23### 1. Assess
24- What is changing?
25- Who is affected?
26- How significant is the change? (Low / Medium / High)
27- What resistance should we expect?

1. Assess

  • What is changing?
  • Who is affected?
  • How significant is the change? (Low / Medium / High)
  • What resistance should we expect?
Raw lines 23 to 28
29### 2. Plan
30- 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 milestones

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
Raw lines 29 to 34
35### 3. Execute
36- Announce and explain the "why"
37- Train and support
38- Monitor adoption
39- Address resistance

3. Execute

  • Announce and explain the "why"
  • Train and support
  • Monitor adoption
  • Address resistance
Raw lines 35 to 40
41### 4. Sustain
42- Measure adoption and effectiveness
43- Reinforce new behaviors
44- Address lingering issues
45- Document lessons learned

4. Sustain

  • Measure adoption and effectiveness
  • Reinforce new behaviors
  • Address lingering issues
  • Document lessons learned
Raw lines 41 to 46
47## Communication Principles
49- Explain the **why** before the **what**
50- Communicate early and often
51- Use multiple channels
52- Acknowledge what's being lost, not just what's being gained
53- Provide a clear path for questions and concerns

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
Raw lines 47 to 54
55## Output
57```markdown
58## Change Request: [Title]
59**Requester:** [Name] | **Date:** [Date] | **Priority:** [Critical/High/Medium/Low]
60**Status:** Draft | Pending Approval | Approved | In Progress | Complete
62### Description
63[What is changing and why]
65### Business Justification
66[Why this change is needed — cost savings, compliance, efficiency, risk reduction]
68### Impact Analysis
69| 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] |
76### Risk Assessment
77| Risk | Likelihood | Impact | Mitigation |
78|------|-----------|--------|------------|
79| [Risk] | [H/M/L] | [H/M/L] | [How to mitigate] |
81### Implementation Plan
82| Step | Owner | Timeline | Dependencies |
83|------|-------|----------|--------------|
84| [Step] | [Person] | [Date] | [What it depends on] |
86### Communication Plan
87| Audience | Message | Channel | Timing |
88|----------|---------|---------|--------|
89| [Who] | [What to tell them] | [How] | [When] |
91### Rollback Plan
92[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]
97### Approvals Required
98| Approver | Role | Status |
99|----------|------|--------|
100| [Name] | [Role] | Pending |
101```

Output

## Change Request: [Title]
**Requester:** [Name] | **Date:** [Date] | **Priority:** [Critical/High/Medium/Low]
**Status:** Draft | Pending Approval | Approved | In Progress | Complete

### Description
[What is changing and why]

### Business Justification
[Why this change is needed — cost savings, compliance, efficiency, risk reduction]

### Impact Analysis
| Area | Impact | Details |
|------|--------|---------|
| Users | [High/Med/Low/None] | [Who is affected and how] |
| Systems | [High/Med/Low/None] | [What systems are affected] |
| Processes | [High/Med/Low/None] | [What workflows change] |
| Cost | [High/Med/Low/None] | [Budget impact] |

### Risk Assessment
| Risk | Likelihood | Impact | Mitigation |
|------|-----------|--------|------------|
| [Risk] | [H/M/L] | [H/M/L] | [How to mitigate] |

### Implementation Plan
| Step | Owner | Timeline | Dependencies |
|------|-------|----------|--------------|
| [Step] | [Person] | [Date] | [What it depends on] |

### Communication Plan
| Audience | Message | Channel | Timing |
|----------|---------|---------|--------|
| [Who] | [What to tell them] | [How] | [When] |

### Rollback Plan
[Step-by-step plan to reverse the change if needed]
- Trigger: [When to roll back]
- Steps: [How to roll back]
- Verification: [How to confirm rollback worked]

### Approvals Required
| Approver | Role | Status |
|----------|------|--------|
| [Name] | [Role] | Pending |
Raw lines 55 to 102
103## If Connectors Available
105If **~~ITSM** is connected:
106- Create the change request ticket automatically
107- Pull change advisory board schedule and approval workflows
109If **~~project tracker** is connected:
110- Link to related implementation tasks and dependencies
111- Track change progress against milestones
113If **~~chat** is connected:
114- Draft stakeholder notifications for the communication plan
115- Post change updates to the relevant team channels

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
Raw lines 103 to 116
Uses an outside tool ~~project :109
Uses an outside tool ~~chat :113
117## Tips
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.

Tips

  1. Be specific about impact — "Everyone" is not an impact assessment. "200 users in the billing team" is.
  2. Always have a rollback plan — Even if you're confident, plan for failure.
  3. Communicate early — Surprises create resistance. Previews create buy-in.
Raw lines 117 to 121

From anthropics/knowledge-work-plugins at 2574e29, 2026-10-27. Skills read by DeepSeek V4.1 Flash on 2026-11-04. Summary and techniques by Claude Opus 5.5 on 2026-11-06.