Change Management Cabinet

Change Management Cabinet

v0.1.0

Structured change request documentation, risk scoring, and CAB approval routing for IT and DevOps teams. A QA reviewer agent validates every change packet for completeness and risk before a workflow agent routes it to the right approvers and schedules CAB review. Keep ServiceNow as your ITSM system of record; replace the inconsistent change forms, the forgotten rollback plans, and the CAB scheduling chaos around them.

itdevopschange-managementcabrisk-assessmententerprisecabinet
2 agents2 jobs1 cabinets3 pages
cabinet /change-packet
change-management app preview

Change Management Cabinet

it

agents

🔍

Change Reviewer

.agents/change-reviewer/

Change Packet Review

📅

Change Workflow Agent

.agents/change-workflow/

Weekly Change Calendar

0 8 * * 1

2

Agents

2

Jobs

1

Depts

3

Pages

Change Management Cabinet
🔍 Change Reviewer
📅 Change Workflow Agent
Change Packet Review
Weekly Change Calendar
🔍Change Reviewerlead

Receives every change request, validates completeness, scores risk using the standard matrix, determines change type, and blocks incomplete packets from reaching the CAB or production.

📅Change Workflow Agentspecialist

Routes validated change packets to the right approvers, schedules CAB, tracks the approval chain, and maintains the weekly change calendar.

0 8 * * 1
Change Packet Reviewpaused

Weekly Change Calendaractive

Change Management Cabinet

Structured change request documentation, risk scoring, and CAB approval routing for IT and DevOps teams. Every change — database migration, infra update, config push, major deploy — gets a complete packet: what's changing, why, what could go wrong, rollout steps, rollback plan, and who needs to approve. The QA reviewer agent validates completeness before anyone wastes time in a CAB meeting. Every packet is a file.

Keep ServiceNow as your ITSM system of record. Replace the inconsistent change forms, the forgotten rollback plans, the CAB prep that happens in a chat thread, and the "who approved this?" question during an incident.

The team

  • [[.agents/change-reviewer]] — Change Reviewer (lead). Receives every change request, validates completeness against the required fields, scores risk using the standard matrix, and determines the change type (standard/normal/emergency). Blocks incomplete packets from reaching CAB.
  • [[.agents/change-workflow]] — Change Workflow Agent. Routes the validated packet to the right approvers, schedules CAB if required, tracks the approval chain, and updates the change calendar.

Recurring rhythm

Cadence Job Owner Output
On-demand (per change) [[.jobs/change-packet-review]] Change Reviewer Change packet in /changes/<change-id>/packet.md
Weekly (Mon 08:00) [[.jobs/weekly-change-calendar]] Change Workflow Weekly change calendar in /reports/change-calendar.md

How to run the demo

  1. Open the [[change-packet]] — a complete change packet for CHG-2026-0312: change header, risk assessment, affected systems, rollout steps, rollback plan, approval chain, CAB schedule, and current status.
  2. Browse /changes/ — one directory per change, each containing the full packet and approval history.
  3. Open /reports/change-calendar.md — the weekly view of scheduled changes and CAB meeting agenda.

Connectors

Required: ServiceNow (change record sync and CMDB context), GitHub (deploy PRs, commit context for code changes). Recommended: Jira (linked issues and release notes), Slack (CAB notifications, approval requests), PagerDuty or Opsgenie (freeze windows, on-call context), Terraform Cloud or Spacelift (infra change context).

Install
$ git clone --filter=blob:none --sparse https://github.com/hilash/cabinets.git && cd cabinets && git sparse-checkout set change-management