anthropics/knowledge-work-plugins

change-request

Create a change management request with impact analysis and rollback plan.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill change-request

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

/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.

タスクに関連する項目

同じリポジトリから

関連する Skills

すべての Skills
anthropics
公式

process-doc

Document a business process — flowcharts, RACI, and SOPs. Use when formalizing a process that lives in someone's head, building a RACI to clarify who owns what, writing an SOP for a handoff or audit, or capturing the exceptions and edge cases of how work actually gets done.

1時間の導入数
1
GitHub Stars
3.7万
更新日
11月20日
anthropics
公式

data-visualization

Create effective data visualizations with Python (matplotlib, seaborn, plotly). Use when building charts, choosing the right chart type for a dataset, creating publication-quality figures, or applying design principles like accessibility and color theory.

1時間の導入数
5
GitHub Stars
3.7万
更新日
11月20日
anthropics
公式

accessibility-review

Run a WCAG 2.1 AA accessibility audit on a design or page. Trigger with "audit accessibility", "check a11y", "is this accessible?", or when reviewing a design for color contrast, keyboard navigation, touch target size, or screen reader behavior before handoff.

1時間の導入数
4
GitHub Stars
3.7万
更新日
11月20日
anthropics
公式

sql-queries

Write correct, performant SQL across all major data warehouse dialects (Snowflake, BigQuery, Databricks, PostgreSQL, etc.). Use when writing queries, optimizing slow SQL, translating between dialects, or building complex analytical queries with CTEs, window functions, or aggregations.

1時間の導入数
4
GitHub Stars
3.7万
更新日
11月20日