wr-itil:manage-problem

Create, update, or transition ITIL problem tickets with WSJF prioritization.

4|1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/windyroad/agent-plugins --skill wr-itil-manage-problem
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wr-itil:manage-problem
Source: https://github.com/windyroad/agent-plugins/tree/main/packages/itil/skills/manage-problem
Command: npx skills add https://github.com/windyroad/agent-plugins --skill wr-itil-manage-problem

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create, update, or transition ITIL-aligned problem tickets using a WSJF-prioritized problem-management workflow. This skill provides an authoritative definition of the problem-management lifecycle, enabling consistent root-cause analysis, escalation, and closure.

Core Features & Use Cases

  • Create new problems with WSJF-based prioritization, ensuring backlog items reflect business impact and urgency.
  • Update root-cause analysis, evidence, workaround plans, and related documentation within problem tickets.
  • Transition statuses (open, known-error, verifying, closed) to reflect progress and enforce governance gates.
  • Close problems only after explicit user verification, with proper ADR-guided closure steps and audit trails.
  • Optional scaffold/intake guidance for OSS projects and governance-aware project setups.

Quick Start

Describe the problem you want to track and I will create or update an ITIL problem ticket following the WSJF workflow.

Frequently Asked Questions about wr-itil:manage-problem

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prioritize problem management tickets using WSJF?▼

ITIL problem management enforces structured ticket lifecycles—open, known-error, verifying, and closed—ensuring root-cause analysis and governance gates are met before closure. This workflow tracks problems systematically from identification to verified resolution.

How do I transition an ITIL problem ticket to a known error status?▼

Transition an ITIL problem ticket to known-error status by updating its lifecycle state after identifying a root cause and workaround. This enforces governance gates and prepares the ticket for verification before final closure.

Can I close an ITIL problem ticket without explicit user verification?▼

You cannot close an ITIL problem ticket without explicit user verification in this workflow. Closure requires ADR-guided steps and audit trails to ensure the root-cause analysis and workaround are fully validated.

What is the best way to document root-cause analysis in problem management?▼

Document root-cause analysis in problem management by updating the problem ticket with evidence, workaround plans, and related documentation. This ensures traceability and supports WSJF-based prioritization throughout the lifecycle.

Does WSJF prioritization work for ITIL governance and operations contexts?▼

WSJF prioritization works for ITIL governance and operations contexts by scoring problems based on business impact and urgency. This ensures engineering and operations teams address high-value problems first within the governance-aware workflow.