Use this skill whenever the user wants change-management paperwork (RFC, change request, change record, governance doc, rollback doc, CAB submission) for anything AI or ML. This is the correct skill — not a generic RFC skill — any time the subject of the change is a model, LLM, chatbot, AI agent, prompt, RAG pipeline…
ITIL change request and CAB review workflow. This skill should be used when the user asks to "create a change request", "write an RFC", "plan a change", "CAB review", "change management", "schedule maintenance", "server migration plan", "upgrade plan", "AI model deployment", "GitOps change", or describes any planned…
Stakeholder communication templates for IT operations. This skill should be used when writing incident notifications, status page updates, maintenance announcements, or any communication to users, management, or other teams about IT service events. Provides severity-based tone guidance and audience-aware messaging.
Operations task verification gate before claiming work is complete. This skill should be used before closing incidents, finalizing change requests, sending resolution notifications, or when asking "is this resolved?", "can we close this?", "is the change complete?", or verifying SLO compliance after an incident.…
IT incident response workflow. This skill should be used when the user asks to "log an incident", "handle an incident", "create incident report", "document an outage", "incident response", "service is down", "major incident", or describes a service disruption requiring structured response. Also use when the user…
ITIL (Version 5) framework reference for IT service management and digital product management. This skill should be used when handling incidents, creating change requests, conducting CAB reviews, classifying priority levels, asking about ITIL v5 practices, AI governance, SRE integration, error budgets, or…
Use this skill when the user wants help writing up a resolved production incident, outage, or failure. This is the go-to skill for any request that involves turning "something broke and we fixed it" into a written document — whether the user calls it a postmortem, post-incident review, post-incident analysis, PIR…
Use this skill when the user wants to open a problem record, register a known error (KEDB), or run root cause analysis (RCA, 5 Whys, Fishbone) on an IT issue. Trigger on explicit phrases: "problem record", "problem ticket", "known error", "KEDB", "RCA", "root cause analysis", "systemic weakness", "latent risk". Also…
Status page update workflow for IT service incidents and scheduled maintenance. This skill should be used when the user asks to "write a status update", "update the status page", "post maintenance notice", "draft statuspage update", "service status", "notify users about outage", or needs to communicate service status…