What problem does it solve? Changes to running production systems often happen without consistent classification, approval, or recording, making it impossible to audit what changed, when, why, and how to undo it. This Skill enforces disciplined operational change management so every change is classified, approved at the right level, executed in a defined window, and recorded with a rollback reference. ## Core Features & Use Cases - Change Classification: Categorizes changes as standard (pre-approved pattern), normal (reviewed), or emergency (expedited with retro-approval) so discipline scales with risk. - Change Recording & Verification Linkage: Records what, why, who, when, risk, and rollback reference for every change, and links post-change verification to the record. - Emergency-Change Handling: Routes incident-driven emergency changes through retrospective review and future-prevention classification. - Use Case: During incident response, an engineer applies an emergency configuration fix to production. This Skill ensures the change is recorded, linked to verification, and closed with a retrospective review instead of disappearing untracked. ## Quick Start Use the Forge-Operational-Change-Management skill to classify and record a planned configuration change to the production database, including its approval level, change window, and rollback reference.
