it-change-release-control

Plans, approves, executes, and validates enterprise IT changes with rollback and risk controls.

Updated Jun 21, 2026
One-click install
npx skills add https://github.com/lwokeray/cowork-plugins --skill it-change-release-control-lwokeray
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: it-change-release-control
Source: https://github.com/lwokeray/cowork-plugins/tree/main/plugins/it-operations-cowork/skills/it-change-release-control
Command: npx skills add https://github.com/lwokeray/cowork-plugins --skill it-change-release-control-lwokeray

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? IT changes and releases often fail due to missing risk assessment, unclear rollback plans, skipped approvals, or unverified execution. This Skill structures the entire change lifecycle so every production change is scoped, authorized, reversible, and validated against real service behavior. ## Core Features & Use Cases - Change Classification & Risk Assessment: Categorizes changes as Standard, Normal, or Emergency and scores risk by likelihood, impact, detectability, reversibility, novelty, and blast radius. - Approval & Rollback Governance: Enforces separation of duties, CAB preparation, maintenance windows, and a rollback quality gate covering restore points, data reconciliation, and propagation effects. - Execution & Validation Workflow: Guides step-by-step implementation with checkpoints, post-change validation of configuration, runtime, user transactions, and monitoring, plus structured closure reporting. - Use Case: Before deploying a firewall rule update across production regions, use this Skill to build the change record, verify test evidence, obtain scoped approvals, define rollback triggers, and validate each batch with per-target results. ## Quick Start Ask the assistant to prepare a change plan with risk assessment, approval requirements, rollback steps, and validation criteria for your upcoming production deployment.

Frequently Asked Questions about it-change-release-control

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

FAQPage Schema
How do I create an IT change management plan?▼

Define the business outcome, exact scope, current and desired state, risk and blast radius, approvals, step-by-step implementation with checkpoints, rollback triggers and steps, and validation criteria. This Skill walks through each stage and produces a structured change record.

What should a rollback plan include for production changes?▼

A valid rollback plan states the exact restore point, how post-change data is reconciled, identity/DNS/certificate propagation effects, estimated rollback time, trigger authority, and post-rollback validation. Simply redeploying the previous version is insufficient when state or schema changed.

How are standard, normal, and emergency changes classified?▼

Standard changes are pre-authorized, repeatable, low-risk, and proven. Normal changes require risk-appropriate assessment and approval. Emergency changes restore service urgently with retrospective review. Novel or high-impact changes must not be labeled standard to bypass governance.

Does this Skill execute changes automatically?▼

No. It plans and supports authorized execution but never executes because a plan exists. It confirms authorization and maintenance windows first, stops on rollback triggers, and respects policy denials or insufficient permissions without workarounds.

How do I validate a change after deployment?▼

Validate by reading back effective configuration from authoritative state, checking runtime behavior and dependencies, executing a real user transaction, confirming security controls, and monitoring through the agreed window. A successful API response alone is not proof of successful delivery.

What happens when a partial batch failure occurs during deployment?▼

Stop or continue according to the predeclared failure threshold defined in the change plan. Report exact per-target results for every system in the batch, and never silently widen scope or skip planned pilot gates.