---
id: daily-change-request
name: "change-request"
url: https://skills.yangsir.net/skill/daily-change-request
author: anthropics
domain: ai-project-management-collaboration
tags: ["devops", "automation", "risk-management", "change-management"]
install_count: 2800
rating: 4.40 (20 reviews)
github: https://github.com/anthropics/knowledge-work-plugins
---

# change-request

> 创建结构化的变更请求，包含影响分析、风险评估、回滚计划和审批流程，确保系统变更安全可控

**Stats**: 2,800 installs · 4.4/5 (20 reviews)

## Before / After 对比

### 变更请求创建

**Before**:

手动分析变更范围和影响系统，评估潜在风险和依赖关系，编写回滚方案，按照模板整理成正式文档，创建一个完整的 CR 需要 30-45 分钟

**After**:

描述变更内容，自动分析影响范围和依赖关系，生成包含风险评估、回滚方案和审批流程的结构化 CR，8 分钟完成

| Metric | Before | After | Change |
|---|---|---|---|
| 创建时间 | 38分钟 | 8分钟 | -79% |

## Readme

# change-request

# /change-request

If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](https://github.com/anthropics/knowledge-work-plugins/blob/HEAD/operations/skills/change-request/../../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.

Weekly Installs317Repository[anthropics/know…-plugins](https://github.com/anthropics/knowledge-work-plugins)GitHub Stars10.6KFirst SeenMar 13, 2026Security Audits[Gen Agent Trust HubPass](/anthropics/knowledge-work-plugins/change-request/security/agent-trust-hub)[SocketPass](/anthropics/knowledge-work-plugins/change-request/security/socket)[SnykPass](/anthropics/knowledge-work-plugins/change-request/security/snyk)Installed oncodex303gemini-cli300opencode299cursor299kimi-cli298github-copilot298

---
*Source: https://skills.yangsir.net/skill/daily-change-request*
*Markdown mirror: https://skills.yangsir.net/api/skill/daily-change-request/markdown*