change-advisory-prep
/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.
- Author
- kesslernity ↗
- Repository
- awesome-copilot-cowork-bots ↗
- Licence
- MIT
- Last repository change
- 05.11.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 05.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
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.
Original author description
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.
How it works
- Inputs
- Procedure
- Output
- Definition of done
- When there is no data
- Boundaries
- Self-check
SKILL.md preview
--- name: change-advisory-prep description: 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. --- # 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, and who has already approved. 3. **Mark every missing field MISSING.** Do not infer a rollback plan, ever. An inferred rollback plan is the single most dangerous thing this skill could produce. 4. **Cross-reference** each change against prior incidents touching the same system, through Enterprise Search, and note them as context rather than as objections. 5. **Order** by stated risk, then by blast radius implied by the affected systems. 6. **Write** the pack, and list separately every change arriving with a missing required field. ## Output | Change | Owner | Window | Systems | Stated risk | Rollback | Prior incidents | Missing | Then: changes ready for the board, changes with missing fields, and prior-incident context. ## Definition of done Every change has every required field either filled from evidence or marked MISSING, and the missing list is surfaced first because it is the board's real agenda. **A board with nothing to review is fine.** Say so. ## When there is no data - No changes found: state the window searched. - A change with only a title: list it with everything MISSING. Do not quietly drop it. - No prior incidents found for a system: say "none found", which is different from "none exist". ## Boundaries - **Never approve, reject or schedule a change.** The board decides. - **Never write a rollback plan.** Report its absence. - Never state a risk rating of your own. Report the proposer's and say it is theirs. - **Draft only.** The pack goes to the user for circulation behind approval. ## Self-check - Did I infer any rollback plan or risk rating? If so, remove it. - Is the missing-fields list first? - Is prior-incident context labelled as context, not objection?
Files in this package (2)
- SKILL.md 3 KB
- references/config.md 1 KB
Versions
The database has no other skills named change-advisory-prep.
Database snapshot: 13.11.2026 · package version 1850579ba703 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100cab-rfc-drafter
Conducts structured change management interviews, audits proposed maintenance windows, calculates 4-dimension ITIL risk scores, and drafts audit-ready Change Advisory Board (CAB) Request for Change (RFC) packages with explicit rollback plans. Use whenever drafting an RFC,… - 100change-request
Create a change management request with impact analysis and rollback plan. Use when proposing a system or process change that needs approval, preparing a change record for CAB review, documenting risk and rollback steps before a deployment, or planning stakeholder communications for a rollout. - 100board-deck
Builds the board pack and the live board deck: a CEO letter that states the condition of the company in prose, a dashboard whose metrics and definitions never move, financials tied to one set of numbers, decisions framed with resolution language ready to be minuted, and a status… - 100advisory-session
Prepares an advisory or board-style session: mandate, member contribution map, agenda, one action record with single owners, and a handoff, keeping what was said apart from AI advice. Use when an advisory group meets. Invites no one. - 100change-management
Implement change management processes. Configure CAB reviews, change windows, and rollback procedures. Use when managing production changes. - 100change-management
Implement change management processes. Configure CAB reviews, change windows, and rollback procedures. Use when managing production changes.