Overview

This skill enables a formal change management process for production systems. It defines a five-step workflow (request, review, schedule, implement, post-review) and classifies changes as Standard, Normal, or Emergency to determine approvals, windows, and rollback needs.

How This Skill Works

It uses a YAML-based change_workflow with five stages: 1_request, 2_review, 3_schedule, 4_implement, 5_review. The process enforces CAB approval for high-risk changes, establishes change windows, and requires a rollback plan and testing evidence in the request and PR templates, followed by a post-implementation review.

When to Use It

• Deploying a security patch to production during a scheduled window
• Making a production configuration change with risk assessment and approvals
• Performing routine low-risk changes (Standard) with pre-approved procedures
• Handling an emergency fix that requires expedited CAB approval
• Conducting planned maintenance with stakeholder communication and rollback readiness

Quick Start

1. Step 1: Prepare change_workflow with description, risk assessment, rollback plan, and testing evidence
2. Step 2: Submit for review and obtain CAB approval if high risk; set change window and notify stakeholders
3. Step 3: Implement the change, verify success, update documentation, and perform post-implementation review

Best Practices

• Clear change categories
• Required approvals by risk
• Rollback procedures documented
• Post-change verification
• Change freeze windows

Example Use Cases

• Patching a production server using a standard change with pre-approved rollback
• Updating a config parameter with normal risk and CAB approval
• Deploying a security patch during a CAB-approved change window
• Executing an emergency security fix with expedited CAB approval
• Documenting rollback and conducting post-change review after deployment

Frequently Asked Questions