change-request

Q: How do I install change-request?

Run npx skills add https://github.com/anthropics/knowledge-work-plugins --skill change-request in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/change-request/ (personal) or .claude/skills/change-request/ (project).

by anthropics OfficialCode Quality & Workflow

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.

Installs: 2.9K
Last 24h: +9
Trending rank: #9022
Security: Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/anthropics/knowledge-work-plugins --skill change-request

01
Install
Run the command in your project. The CLI asks which agents to install for.
02
Describe the task
Ask your agent for something this skill covers. It loads change-request automatically when relevant.
03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

/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] | **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 |

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.

FAQ

What does the change-request skill do?

How do I install change-request?

Run npx skills add https://github.com/anthropics/knowledge-work-plugins --skill change-request in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/change-request/ (personal) or .claude/skills/change-request/ (project).

Which AI agents can use change-request?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is change-request safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains change-request?

It is published by anthropics in anthropics/knowledge-work-plugins, and it is an official skill from the maker of the technology it covers. It has 2,861 recorded installs.