wr-itil:review-problems

Re-score ITIL problem tickets against RISK-POLICY.md and update backlog files.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Re-assess every open and known-error problem ticket in docs/problems/ — re-read RISK-POLICY.md, re-rate Impact × Likelihood, re-estimate Effort, recalculate WSJF, surface pending verifications, auto-transition Open → Known Error where warranted, and rewrite docs/problems/README.md with the refreshed ranking. Writes to problem files and the README cache; commits the refresh per ADR-014.

Core Features & Use Cases

  • Re-scores the backlog against current risk policy and ranking rules.
  • Auto-transitions Open tickets to Known Error when root cause plus workaround are documented.
  • Rewrites docs/problems/README.md with the refreshed WSJF backlog and verification surfaces.

Quick Start

Run the wr-itil:review-problems skill to refresh WSJF rankings and update the problems README.

Frequently Asked Questions about wr-itil:review-problems

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

FAQPage Schema
How do I recalculate WSJF scores for an ITIL problem backlog?

To recalculate WSJF scores for an ITIL problem backlog, the skill re-evaluates open and known-error tickets against current risk policies to re-rate Impact, Likelihood, and Effort, then rewrites the backlog documents with refreshed rankings.

How does automated problem management transition open tickets to known errors?

Automated problem management transitions open tickets to known errors by verifying that both the root cause and workaround are fully documented, then auto-transitioning the status and updating the backlog files via git.

What is the best way to refresh a risk policy verification backlog?

The best way to refresh a risk policy verification backlog is to re-score open tickets against the current RISK-POLICY.md, surface pending verifications, and rewrite the README cache with updated WSJF rankings.

Can I automate governance updates for open and verifying ITIL tickets?

Yes, you can automate governance updates for open and verifying ITIL tickets by re-scoring them against current risk policies, calculating WSJF, and persisting the backlog changes via git staged per ADR rules.

Do I need a RISK-POLICY.md file to re-score my problem backlog?

Yes, you need a RISK-POLICY.md file to re-score your problem backlog, because the skill uses it as the baseline to re-evaluate Impact and Likelihood ratings for open and known-error tickets.