Change Request
AnthropicOfficialPublished by Anthropic
- Skill
- Content generator
- Business and productivity
- Apache-2.0
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
The change-request skill provides a standardized framework for documenting and proposing organizational or system changes. It guides users through the assess-plan-execute-sustain methodology, ensuring that every change request includes critical components such as business justification, impact analysis, risk mitigation, and a formal rollback plan. By following this structured approach, users can prepare professional documentation suitable for Change Advisory Board (CAB) reviews and stakeholder communication.
What it does
- Generates a comprehensive change request document template.
- Facilitates structured impact analysis across users, systems, and processes.
- Provides a framework for risk assessment and mitigation planning.
- Outlines a clear implementation and communication strategy.
- Defines mandatory rollback procedures to ensure system stability.
- Supports integration with ITSM and project tracking tools for automated ticket creation.
When to use it
- When proposing a system or process change that requires formal approval.
- When preparing documentation for a Change Advisory Board (CAB) review.
- When planning a deployment and needing to document risks and rollback steps.
- When developing a communication plan for a rollout to stakeholders.
Advantages
- Ensures consistency in change management documentation.
- Promotes proactive risk management through mandatory rollback planning.
- Encourages clear communication by focusing on the 'why' before the 'what'.
- Reduces resistance by facilitating structured stakeholder engagement.
Usage examples
- “Create a change request for migrating our legacy database to a cloud-based solution.”
- Generates a detailed markdown document outlining the migration impact, risks, implementation timeline, and a specific rollback plan to revert to the legacy database if the migration fails.
- “Draft a change request for updating the company's remote work policy.”
- Produces a structured request including the business justification, an impact analysis on employee workflows, and a communication plan to inform staff about the policy changes.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/anthropics/change-request/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip change-request.zip -d .agents/skills
Documentation by Anthropic
/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 $ARGUMENTSChange 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.
Files
- ATTRIBUTION.mdAdded by AutoGineer905 B
- LICENSELicence file added by AutoGineer11.3 KiB
- SKILL.md3.7 KiB
SKILL.md
/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 $ARGUMENTSChange 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.
Requirements and compatibility
Written for: Claude Code, Claude apps
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Claude Code frontmatter
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Published by
- Anthropic
- Publisher
- Anthropic (Official)
- Source
- anthropics/knowledge-work-plugins · operations/skills/change-request · commit e050c2e
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Anthropic.
Related skills
Internal Comms
AnthropicOfficial
A structured framework for drafting professional internal communications across various organizational formats.
Business and productivityClaude CodeClaude appsOpenAI Codex+14 moreApache-2.0GitHub stars of the source repository188.6k
To Tickets
Matt Pocock· Community
Break complex plans into actionable, dependency-aware tracer-bullet tickets for your issue tracker.
Business and productivityClaude CodeClaude appsOpenAI Codex+14 moreMITGitHub stars of the source repository317.5k
To Questionnaire
Matt Pocock· Community
Generate structured discovery questionnaires to extract missing information from stakeholders.
Business and productivityClaude CodeClaude appsOpenAI Codex+14 moreMITGitHub stars of the source repository317.5k
Events
Corey Haines· Community
A comprehensive framework for planning, executing, and measuring event-driven marketing to drive measurable business pipeline.
Business and productivityClaude CodeClaude appsOpenAI Codex+14 moreMITGitHub stars of the source repository59k
Office Hours
AnthropicOfficial
Facilitate team support by setting up and managing recurring office hours for collaborative problem-solving.
Business and productivityClaude CodeClaude appsOpenAI Codex+14 moreApache-2.0GitHub stars of the source repository46.3k
Hackathon
AnthropicOfficial
Plan and organize a team hackathon, either by sourcing projects from your existing backlog or through open-ended creative experimentation.
Business and productivityClaude CodeClaude appsOpenAI Codex+14 moreApache-2.0GitHub stars of the source repository46.3k
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download change-request.zip