change-request

Generate CAB-ready change management documents with impact analysis, risk assessment, and rollback planning.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/sun2443/designer-skills --skill change-request-sun2443
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: change-request
Source: https://github.com/sun2443/designer-skills/tree/main/operations/skills/change-request
Command: npx skills add https://github.com/sun2443/designer-skills --skill change-request-sun2443

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of unclear change proposals by creating a structured change management request that captures impact, risk, and rollback expectations before approval and deployment.

Core Features & Use Cases

  • Impact analysis: Documents which users, systems, processes, and cost areas are affected, including practical details for decision makers.
  • Risk assessment and rollback planning: Identifies risks with likelihood and impact and defines step-by-step rollback triggers, actions, and verification.
  • CAB-ready communication: Builds stakeholder communication and sustainment steps so teams adopt the change and measure effectiveness after release.
  • Use Case: Proposing a workflow or system/process change for CAB review, including what will change, who it affects, how it will be communicated, and how to safely revert if outcomes are worse than expected.

Quick Start

Create a complete change request by running /change-request with a clear description of the proposed system or process change.

Frequently Asked Questions about change-request

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is a CAB-ready change management document?

A CAB-ready change management document is a structured proposal that captures impact analysis, risk assessment, and rollback planning to secure approval before system or process deployment.

How do I write a change request that includes impact analysis and rollback planning?

You can generate a change request by providing a clear description of the proposed change, which produces structured assess-plan-execute-sustain sections with tables for impacts, risks, and rollback steps.

When do I need a rollback plan for a system or process change?

A rollback plan is needed when proposing a change for CAB review, ensuring you define step-by-step rollback triggers, actions, and verification in case outcomes are worse than expected.

Does this approach cover stakeholder communication for change rollouts?

Yes, this approach builds stakeholder communication and sustainment steps so teams adopt the change and can measure effectiveness after the release is deployed.

Can I use this for both system and process change proposals?

Yes, you can use this for both system and process change proposals, as it documents affected users, systems, cost areas, and practical details required for CAB review and deployment planning.

What is the best way to structure risk assessment for a deployment plan?

The best way to structure risk assessment is using tables that identify specific risks alongside their likelihood and impact, which clarifies rollback expectations and decision-making for stakeholders.