Individual skill

change-advisory-prep

Assembles the pack for the next change advisory board from the change requests, threads and documents already circulating, with the risk and rollback position for each change stated or marked missing. Use when the user asks to prepare for CAB, build the change board pack, review upcoming changes, or says a change board is coming up.

packs/it-ops/change-advisory-prep/skill/SKILL.md

Read pinned source

Source commit d10af7a3e2da1bdc54d72e6a4af870c2e1212464

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Not checked yet
Last checked: Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 16
Repository last updated: Nov 5, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

agent-skills Repository topic
ai-governance Repository topic
copilot Repository topic
copilot-cowork Repository topic
cowork Repository topic
m365 Repository topic
microsoft-365-copilot Repository topic
microsoft365 Repository topic
skill-md Repository topic
engineering Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 2,742 bytes
references/config.mddoc · 171 bytes

Read excerpt


# Change Advisory Board Prep

Builds the pack from what people actually wrote, and names every change that arrived without a
rollback plan.

## Inputs
- **Email** and Teams traffic about upcoming changes
- **Enterprise Search** for change records, runbooks and prior post-incident notes
- `references/config.md` for the board date, the required fields and the risk vocabulary

## Procedure
1. **Find the changes** proposed for the board window.
2. **For each change, extract the required fields** from config. The usual set: what changes, who
   owns it, the window, affected systems, risk rating as stated by the proposer, rollback plan,