Plan and execute controlled admin changes such as patches, config edits, restarts, upgrades, and rollbacks. Use when CTOX must stage a host or service change, compare current versus target config, verify preconditions, prepare rollback, or drive a maintenance-window task from dry run through post-change verification.
Use this skill when the job is a deliberate state change or a dry-run change plan.
Do not use it as the first choice for scope discovery or generic health review:
discovery_graph when the target surface is still unclearreliability_ops when the main question is healthincident_response when fast stabilization matters more than a planned rolloutThis skill uses the shared SQLite kernel via skill_key=change_lifecycle.
Treat this skill as:
Preferred helper scripts under scripts/:
change_collect.pychange_capture_run.pychange_store.pychange_query.pychange_bootstrap.pyThey are inspectable helpers, not hidden authority. Read or patch them when the change is nontrivial.
change.capture_rawchange.store_capturechange.store_graphchange.querychange.bootstrap_planchange_collect.py or change_capture_run.py.change_request, config_snapshot, change_plan, rollback_bundle, and only an executed change_result if a change really happened.Answer for the operator first.
Use these exact headings:
**Status****State****Scope****Autonomous Actions****Escalation****Current Findings****Next Step**State must be one of:
proposedpreparedexecutedblockedTreat dry runs, staged plans, rollback bundles, and preflight checks as prepared, not executed.
If a change started but is not yet complete, say so explicitly and leave a durable next-work record instead of saying you are "working on it" without closure.
Do not finish the reply until all of the following are true:
State explicitly reflects whether the system changedState is executed, post-change verification is stated in Current Findingsblocked