Itil Expert

ITIL Expert (ITIL 4 & 5)

Overview

This public intake copy packages plugins/antigravity-awesome-skills-claude/skills/itil-expert from https://github.com/sickn33/antigravity-awesome-skills into the native Omni Skills editorial shape without hiding its origin.

Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.

This intake keeps the copied upstream files intact and uses the external_source block in metadata.json plus ORIGIN.md as the provenance anchor for review.

ITIL Expert (ITIL 4 & 5)

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Purpose, Core Capabilities, Expert Instructions, Applicability Suggestions (ITIL 5), Limitations.

When to Use This Skill

Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.

• You are designing or optimizing a Service Value Stream (SVS).
• You need to align IT operations with ITIL 5's Digital Product paradigm.
• You are implementing AI within IT practices and require governance frameworks.
• You need to integrate ESG/Sustainability metrics into Service Level Agreements (SLAs).
• You are preparing for ITIL 4/5 certifications or audit readiness.
• Use when the request clearly matches the imported source intent: Expert advisor for ITIL 4 and ITIL 5 (2026 digital product paradigm), specialized in AI-native governance, sustainability, and value co-creation.

Operating Table

Workflow

This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.

1. Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task.
2. Read the overview and provenance files before loading any copied upstream support files.
3. Load only the references, examples, prompts, or scripts that materially change the outcome for the current request.
4. Execute the upstream workflow while keeping provenance and source boundaries explicit in the working notes.
5. Validate the result against the upstream expectations and the evidence you can point to in the copied files.
6. Escalate or hand off to a related skill when the work moves out of this imported workflow's center of gravity.
7. Before merge or closure, record what was used, what changed, and what the reviewer still needs to verify.

Imported Workflow Notes

Imported: Purpose

To act as a premier consultant for ITIL 4 and the newly released ITIL 5 frameworks. This skill provides authoritative strategic and operational guidance on evolving ITIL 4's Service Value System into ITIL 5's Digital Product & Service Management (DPSM) paradigm. It focuses on integrating AI governance, sustainability (ESG) imperatives, and product-centric lifecycle management into modern technical environments.

Examples

Example 1: Ask for the upstream workflow directly

Use @itil-expert to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.

Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.

Example 2: Ask for a provenance-grounded review

Review @itil-expert against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.

Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.

Example 3: Narrow the copied support files before execution

Use @itil-expert for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.

Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.

Example 4: Build a reviewer packet

Review @itil-expert using the copied upstream files plus provenance, then summarize any gaps before merge.

Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.

Imported Usage Notes

Imported: Strategic Examples

• Designing an AI-Native Service Desk: Map the "Engage" activity to a multi-model AI agent that handles triage, resolution, and sentiment analysis.
• Mapping a DevOps-ITIL Value Stream: Use the "Design & Transition" activity as the automation gate between the CI/CD pipeline and the production environment.

Best Practices

Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.

• Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support.
• Prefer the smallest useful set of support files so the workflow stays auditable and fast to review.
• Keep provenance, source commit, and imported file paths visible in notes and PR descriptions.
• Point directly at the copied upstream files that justify the workflow instead of relying on generic review boilerplate.
• Treat generated examples as scaffolding; adapt them to the concrete task before execution.
• Route to a stronger native skill when architecture, debugging, design, or security concerns become dominant.

Troubleshooting

Problem: The operator skipped the imported context and answered too generically

Symptoms: The result ignores the upstream workflow in plugins/antigravity-awesome-skills-claude/skills/itil-expert, fails to mention provenance, or does not use any copied source files at all. Solution: Re-open metadata.json, ORIGIN.md, and the most relevant copied upstream files. Check the external_source block first, then restate the provenance before continuing.

Problem: The imported workflow feels incomplete during review

Symptoms: Reviewers can see the generated SKILL.md, but they cannot quickly tell which references, examples, or scripts matter for the current task. Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.

Problem: The task drifted into a different specialization

Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.

Related Skills

• @00-andruia-consultant - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @00-andruia-consultant-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @10-andruia-skill-smith - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @10-andruia-skill-smith-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.

Additional Resources

Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.

• itil-5-evolution.md
• itil-usage.md
• README.md
• itil-usage.md
• itil-5-evolution.md

Imported Reference Notes

Imported: References

• ITIL 5 Evolution Guide
• Real-World Usage Scenarios
• ITIL 5 Extension Modules (2026 Edition)

Imported: Core Capabilities

• DPSM Strategy: Advising on the unification of product management and service management.
• AI-Native Governance: Providing frameworks for responsible AI adoption, automated decision-making, and algorithmic ethics.
• Sustainability (ESG) Integration: Embedding circular economy principles and resource efficiency into IT service design.
• Value Stream Mapping: Designing end-to-end value streams that focus on value co-creation.
• Practice Modernization: Updating the 34 ITIL practices for automated, high-velocity, and cloud-native environments (DevOps/SRE/AIOps).
• ISO/IEC 20000 Compliance: Aligning digital product management with international service quality standards.

Imported: Expert Instructions

1. The 7 Guiding Principles in the AI & ITIL 5 Era

Adapt these principles when providing advice on modern digital products:

• Focus on Value (with AI): AI shouldn't just exist; it must directly contribute to the user's value realization. If the AI doesn't improve the outcome, it is waste.
• Start Where You Are: Don't rip and replace ITIL 4; build on the existing Service Value System and identify where AI can augment it.
• Progress Iteratively with Feedback: Use "A/B Testing" and "Canary Deployments" for all new service features.
• Collaborate and Promote Visibility: Use shared dashboards (Grafana/Datadog) to bridge the gap between AI developers and IT operators.
• Think and Work Holistically: Consider the "Four Dimensions" (People, Process, Technology, Partners) especially when AI replaces manual tasks.
• Keep it Simple and Practical: Automate only what is stable. Don't over-engineer AI solutions for complex, low-volume incidents.
• Optimize and Automate: ITIL 5's mantra. First optimize the value stream, then use AI to automate the flow.

2. Digital Product & Service Management (DPSM)

ITIL 5 eliminates the "Service vs Product" silo.

• Product Thinking: Ownership moves from "Service Desks" to "Product Teams" responsible for the entire journey.
• Integrated Lifecycle: Merging Agile/DevOps cycles with the Service Value Chain activities (Design, Build, Support).
• The Digital Product Portfolio: Manage services like an investment portfolio, focusing on ROI, user adoption, and life-cycle cost (TCO).

3. AI Governance & The "Governance of Algorithms" Practice

A dedicated focus on high-fidelity AI management:

• Algorithmic Transparency: Mandating that AI models used for "Change Approvals" or "Resource Allocation" are not "Black Boxes."
• Next Best Action (NBA): In the Service Desk, AI should calculate the NBA for an analyst based on historical resolution data and current context.
• Data Roots: Every "Service Problem" must verify if the root cause was a lack of data quality or a drift in the AI model.

4. Sustainability & Circular IT (ESG)

Sustainability is a primary metric of success in ITIL 5.

• Eco-Design: Every new digital product requires a "Sustainability Impact Assessment" (SIA) before the Build phase.
• Cloud Sustainability: Use region-aware scheduling to run batch jobs in data centers powered by renewable energy.
• CMDB for Asset Life: The CMDB must track the "Embodied Carbon" of all hardware assets from procurement to recycling.

5. Detailed Practice Modernization (High-Velocity IT)

• Monitoring & Event Management: Transition to AIOps where patterns are identified automatically, triggering self-healing value streams.
• Service Configuration Management: Moving to Immutable Infrastructure where changes are never made to a running system; instead, a new "Product Version" is deployed.
• Financial Management: Leveraging Cloud FinOps to manage the variable cost models of modern SaaS and AI compute.

Imported: Applicability Suggestions (ITIL 5)

• High-Velocity Environments: Use ITIL 5 to provide "Continuous Compliance" via automated auditing and policy-as-code.
• Customer Experience (CX): Focus on XLAs (Experience Level Agreements) that measure "Friction" and "Effort" rather than technical uptime.
• Vendor Management: Move to "Partnering for Value" where vendors are measured on their contribution to the organization's sustainability goals.

Imported: Limitations

• This skill provides framework-based guidance and should be verified against local organizational policies and legislation.
• Sustainability metrics are based on industry standards (e.g., GHG Protocol) and should be validated by certified consultants.
• Best used in conjunction with "Agile," "Lean," and "DevOps" expert skills.