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今天更新