Change Request

作者 anthropicsae1513ea94dc无许可证27K 个星标收录于 2026年10月8日更新于 2026年10月8日仓库今天更新

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.

AI 生成的概览

生成结构化的变更管理请求,包含影响分析、风险评估和回滚计划。

功能
该技能按照评估-规划-执行-维持框架生成结构化的变更请求文档。它会填写描述、业务理由、影响分析、风险评估、实施计划、沟通计划、回滚计划和所需审批等部分。它还提供可选的连接器操作,例如创建 ITSM 工单、关联项目跟踪任务以及起草利益相关者通知。
适用场景
适用于提出需要审批的系统或流程变更、为 CAB 评审准备变更记录、在部署前记录风险和回滚步骤,或为上线规划利益相关者沟通。
运行要求
仅包含说明,不附带脚本。可选连接器(ITSM、项目跟踪器、聊天)可扩展功能,但均非必需。

/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

markdown
## 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

  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.

来源与署名

来源:anthropics/knowledge-work-plugins位于operations/skills/change-request提交ae1513e

许可证: 无许可证

内容归原作者所有。SourceWeft 从公开仓库中收录这些内容。

举报或申请下架

更多来自 anthropics/knowledge-work-plugins 的技能

Ticket Deflector

anthropics

精选

Reads a forwarded customer email or ticket, pulls order and refund status from a payments connector (PayPal, Square, or Stripe) or Shopify, account history from the CRM, and open tickets from a support desk (Zoho Desk), drafts a tone-matched reply in the owner's writing voice, and can issue a refund through the payments connector with explicit owner approval. With Shopify connected it also runs a proactive order-triage mode that surfaces orders needing attention — unfulfilled past the promised window, payment problems, pending refunds, stuck shipments — and drafts the next action for each before the customer has to ask. Use when the user says "draft a response," "answer this customer," "where's my order," "I want a refund," "check my orders," or "anything about to blow up."

待分类27K今天更新

Tax Season Organizer

anthropics

精选

Prepares tax-season materials for the owner's accountant, not tax advice. US federal tax; a non-US business gets its closed-books packet instead. Two modes: (1) quarterly estimated tax from YTD net income in the ledger (MYOB, NetSuite, QuickBooks, Xero, or Zoho Books); (2) year-end 1099 prep, scanning the ledger, PayPal, and Stripe for contractors paid over USD 600 into a 1099-NEC list with missing W-9 flags. Any tax request routes first to /tax-prep, which confirms the books are closed and reconciled before running this skill. Use this skill directly only when the owner says the period's books are already closed: "books are closed, now do the 1099s," "run the quarterly estimate off the closed numbers," or "just the contractor W-9 list."

待分类27K今天更新

Tax Prep

anthropics

精选

基于已结账的账目准备税务材料:季度预估缴税明细,或年终 1099-NEC 清单与会计师资料包。

Business & Finance27K今天更新

Smb Onboard

anthropics

精选

引导小微企业主完成首次设置:连接工具、运行一次体现价值的配方、记录业务背景并设定每周检查节奏。

Productivity & Workflow27K今天更新

Smb Router

anthropics

精选

将小企业主的需求转接到合适的插件技能或命令,并说明可用功能。

Productivity & Workflow27K今天更新

Month End Prep

anthropics

精选

Reconciles the accounting ledger (MYOB, NetSuite, QuickBooks, Xero, or Zoho Books) against PayPal, Shopify, Square, and Stripe settlements, flags transactions that need attention, suspicious duplicates, and missing receipts, then writes a plain-English P&L narrative and exports a close packet (xlsx + one-page PDF). This is the first link of the /close-month command; a request to close the month or the books routes there, and the command runs this skill before refreshing the forecast and distributing the packet. Use this skill directly only when the owner wants the reconciliation alone, with no forecast refresh and no distribution: "just reconcile, no packet," "what's missing from the books," "flag the duplicates and missing receipts," or "write the P&L narrative for this month."

待分类27K今天更新