change-request
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
Chinese/change-request
/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.
若你看到不熟悉的占位符或需要查看已连接的工具，请参阅CONNECTORS.md。
创建包含影响分析、风险评估和回滚计划的结构化变更管理请求。
Usage
使用方法
/change-request $ARGUMENTS/change-request $ARGUMENTSChange Management Framework
变更管理框架
Apply the assess-plan-execute-sustain framework when building the request:
构建请求时应用“评估-规划-执行-维持”框架：
1. Assess
1. 评估
- What is changing?
- Who is affected?
- How significant is the change? (Low / Medium / High)
- What resistance should we expect?
- 变更内容是什么？
- 哪些对象会受到影响？
- 变更的重要程度如何？（低/中/高）
- 我们预计会遇到哪些阻力？
2. Plan
2. 规划
- 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
3. 执行
- Announce and explain the "why"
- Train and support
- Monitor adoption
- Address resistance
- 宣布并解释变更的“原因”
- 开展培训与支持
- 监控采用情况
- 处理阻力
4. Sustain
4. 维持
- 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
输出格式
markdown
undefinedmarkdown
undefinedChange 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 |
undefined| 审批人 | 角色 | 状态 |
|---|---|---|
| [姓名] | [角色] | 待审批 |
undefinedIf 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
若已连接~~ITSM：
- 自动创建变更请求工单
- 拉取变更咨询委员会（CAB）的日程安排与审批工作流
若已连接~~项目跟踪工具：
- 关联相关的实施任务与依赖项
- 对照里程碑跟踪变更进度
若已连接~~聊天工具：
- 为沟通计划草拟相关方通知
- 将变更更新发布至相关团队频道
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.
- 明确影响范围——“所有人”不是有效的影响评估。“计费团队的200名用户”才是。
- 务必制定回滚计划——即使你信心十足，也要为失败做好预案。
- 尽早沟通——意外会引发阻力，提前预告能争取支持。