Stats
Actions
Tags
From ITIL-assistant
Launch an interactive ITIL v4-compliant Change Request management app. Use this skill whenever the user wants to create, edit, or manage IT change requests for CAB approval. Triggers include: "change request", "CAB submission", "RFC", "request for change", "change management", upgrading servers/databases/applications, infrastructure changes, patch deployments, software rollouts, or any request where an IT team needs formal approval. Use this skill even if the user just says "I need to submit a change" or "open the change request tool".
How this skill is triggered — by the user, by Claude, or both
Slash command
/ITIL-assistant:itil-change-requestThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Launches an interactive Change Request management app. All CR data persists between sessions via `window.storage`.
Launches an interactive Change Request management app. All CR data persists between sessions via window.storage.
When this skill is triggered, read references/cr-app.jsx and present it as a React JSX artifact. Do not collect information inline — the app handles everything.
The app supports:
If the user asks to export a CR as a Word doc:
/mnt/skills/public/docx/SKILL.mdreferences/docx-template.md for structure.docx using docx npm package/mnt/user-data/outputs/Change Requests/{RFC_ID}.docx
/mnt/user-data/outputs/Change Requests/Approved/{RFC_ID}.docxpython scripts/office/validate.pypresent_files| Key | Value |
|---|---|
cr_index | JSON array of RFC IDs |
cr_{id} | JSON — full CR record |
{
"id": "RFC-2026-0042",
"title": "", "changeType": "Normal", "priority": "Medium",
"requestedBy": "", "changeOwner": "",
"dateSubmitted": "2026-03-05",
"affectedSystems": "", "businessJustification": "", "changeDescription": "",
"implSteps": [{ "id": 1, "text": "", "checked": false }],
"rollbackSteps": [{ "id": 1, "text": "", "checked": false }],
"validationItems": [{ "id": 1, "text": "", "checked": false }],
"changeWindow": { "start": "", "duration": "", "maintenanceWindow": "" },
"riskLevel": "Medium", "riskImpact": "", "riskUsers": "", "riskDeps": "",
"approverIds": ["a1"],
"status": "Draft", "cabNotes": "",
"cabHistory": [],
"retrospectiveReview": false,
"createdAt": "2026-03-05T12:00:00Z", "updatedAt": "2026-03-05T12:00:00Z"
}
Draft → Pending CAB Approval → Approved by CAB
→ Rejected
Emergency (changeType === "Emergency"):
Draft → Approved by CAB (auto-approved, retrospectiveReview: true)
/cab-review skill.retrospectiveReview: true.| ID | Name | Role |
|---|---|---|
| a1 | Sarah Johnson | IT Director |
| a2 | Mark Chen | Application Owner |
| a3 | Lisa Patel | Security Lead |
| a4 | David Williams | Infrastructure Manager |
| a5 | Jennifer Torres | Change Manager |
| a6 | Robert Kim | Database Administrator |
| a7 | Amanda Foster | Network Lead |
| a8 | Michael Osei | CISO |
npx claudepluginhub somtimz/plugins --plugin ITIL-assistantGenerates change requests with impact analysis, risk assessment, implementation plans, communication strategies, and rollback steps for system changes, deployments, or CAB reviews.
Routes SDD change actions to phase-specific skills, orchestrating lifecycle from creation, spec review, planning, implementation, verification, and management with validation checks.
Automates the end-to-end change management pipeline: detects changes, classifies levels, drafts CHG records, traces cross-layer impact, and prepares gate approval. Works from diffs, incidents, prompts, or artifact edits.