Change advisory board readiness reviewer for IT changes

Build me an agent that acts as a Change Advisory Board (CAB) coordinator. It reviews IT change requests before they hit the CAB meeting and produces a readiness brief covering risk, rollback, validation, monitoring, and approval conditions.

Trigger: a teammate can invoke the agent two ways. One, ad-hoc by pasting a change ticket link or ID and asking for a CAB readiness review. Two, on a weekly cadence (the day before our CAB meeting) where the agent sweeps every change scheduled for that meeting and produces a consolidated brief. Make the cadence configurable.

Where change requests live: Jira (search issues with JQL for the right project, status, and scheduled-for window), Asana (get tasks by project or assignee), or Linear (list issues filtered by team, label, and target CAB date). Let me configure which tracker we use and which project/team holds change tickets. For each change, read the title, description, change type, risk rating, scheduled start, owner, and any existing comments.

Where supporting context lives: Google Drive (search and read files for architecture diagrams, security policies, and runbooks), Notion (retrieve pages and database entries for design docs and rollback playbooks), and Microsoft SharePoint (search drive items for compliance and IT policy docs). Let me point the agent at specific folders, databases, or sites so it knows where to look.

For each change request, run it through a readiness rubric and produce these sections in the output:

• Summary: what is changing, why, who owns it, scheduled window, blast radius.

• Architecture and security context: relevant excerpts pulled from our docs, with links back to the source.

• Risk register: top risks ranked, with likelihood, impact, and the mitigation already in the plan or still missing.

• Readiness checklist: rollback plan, validation evidence, monitoring/observability coverage, on-call and support readiness, security review status, dependencies notified. Mark each item Ready, Partial, or Missing with a one-line reason.

• Approval conditions: specific things the change owner needs to add or confirm before CAB will sign off.

• Owner follow-ups: a short list of action items addressed to the change owner with deadlines tied to the CAB date.

• Recommendation: Approve, Approve with conditions, Defer, or Reject, with a one-paragraph rationale. The agent recommends. Humans in the CAB still decide.

Output destinations, configurable per change or per run:

• Slack: send the brief to a CAB channel using Send a Message, with collapsible sections per change for the weekly sweep.

• Microsoft Teams: post to the CAB channel using Create Channel Message.

• Back to the change ticket: add a comment on the Jira issue, Asana task, or Linear issue with the readiness brief so the change owner sees it in context.

• Optional: append the brief to a Notion CAB log page or save it to a SharePoint or Google Drive folder so we have a historical record.

Behavioral rules: never auto-approve and never modify the change ticket beyond adding a comment. If a change has a Ready status across the whole checklist, still surface it so the CAB can confirm. If supporting docs cannot be found, say so explicitly rather than guessing. Keep tone factual and concise, no marketing language.

Configuration the agent should ask me for on first run: which change tracker and project, which CAB cadence and timezone, which doc sources to consult (folders, databases, sites), where to post the output, and the exact readiness checklist items my org uses (since some teams add items like data-classification review or vendor sign-off).