change-management

Plan an operational, product, infrastructure, or process change with scope, impact, owners, approvals, rollout, communication, rollback, and verification. Use for change request, change plan, release

SKILL.md

GitHub

Change Management

Make changes explicit, reversible where possible, and observable after rollout.

  1. State the change, rationale, non-goals, affected users/systems, owner, and approval boundary.
  2. Assess impact, dependencies, risks, communications, and maintenance burden.
  3. Define prechecks, phased rollout, success signals, abort criteria, rollback steps, and post-change verification.
  4. Record decisions and unresolved risks in a concise change record.

Never represent a plan as an approval, execute production changes, or send communications without explicit authorization.