wr-itil:work-problem

Select the highest-WSJF ticket and delegate its workflow to manage-problem.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pick the highest-WSJF open or known-error problem ticket and work it end-to-end. This is the singular, interactive entry point — one ticket per invocation, driven by an AskUserQuestion selection when the WSJF ranking is tied.

Core Features & Use Cases

  • Interactive single-ticket workflow: selects the top WSJF ticket and delegates everything to the authoritative manage-problem flow.
  • Structured decision prompts: uses AskUserQuestion to resolve ties and guide next actions, with clear options for different tickets or to switch tasks.
  • Delegation to the canonical workflow: defers actual investigation, root-cause analysis, fix implementation, and release to /wr-itil:manage-problem <NNN> to maintain a single, auditable pipeline.

Quick Start

Invoke /wr-itil:work-problem to start processing the next highest-WSJF ticket.

Frequently Asked Questions about wr-itil:work-problem

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

FAQPage Schema
How do I pick the highest priority problem ticket and work it end-to-end?

To pick the highest priority problem ticket, the workflow selects the top WSJF-ranked ticket and drives the end-to-end investigation, coding, and release execution for that single ticket interactively.

What happens when multiple problem tickets have a tied WSJF ranking?

When WSJF rankings are tied, the workflow uses an interactive AskUserQuestion prompt to present the tied tickets and guide your selection, ensuring you explicitly choose the next problem ticket to process.

How does interactive ticket management differ from automated batch processing?

Interactive ticket management processes one singular problem ticket per invocation with structured decision prompts, whereas automated batch processing handles multiple tickets away from the keyboard without manual scope-change interventions.

Can I switch tasks or change the scope during problem management?

Yes, you can switch tasks or change scope during problem management because the workflow enables structured scope-change prompts, allowing you to select different tickets or redirect the investigation mid-flow.

Does this workflow handle root-cause analysis and release execution directly?

It delegates root-cause analysis, fix implementation, and release execution to the canonical manage-problem pipeline, maintaining a single auditable pipeline rather than executing those steps independently.

When should I use an interactive workflow for problem management instead of full automation?

Use an interactive problem management workflow when you need to manually resolve WSJF ranking ties, guide next actions with structured prompts, and dynamically manage scope changes for singular ticket processing.