wr-itil:transition-problems

Batch-transition ITIL tickets with per-ticket validation and a single commit.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Batch-transition ITIL tickets along the lifecycle in one invocation, eliminating the need to run the per-ticket transition flow N times.

Core Features & Use Cases

  • Parses a list of <NNN> <status> pairs and validates transitions for batch updates.
  • Performs per-ticket transition mechanics inline: discovery, pre-flight checks, external-root-cause detection, rename and metadata edits, and a single final commit.
  • Ideal for closing multiple verifyings or moving several Known Errors through Verification Pending to Closed in one orchestrated run.

Quick Start

Provide a space-separated list of three-digit ticket IDs and target statuses to execute a batch transition.

Frequently Asked Questions about wr-itil:transition-problems

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

FAQPage Schema
How do I batch transition multiple ITIL tickets in one run?

To batch transition ITIL tickets, provide a space-separated list of three-digit ticket IDs and target statuses. The Skill validates each transition, performs pre-flight checks, edits metadata, and commits all updates in a single final batch.

What is the process for moving several Known Errors to Closed simultaneously?

Moving multiple Known Errors to Closed simultaneously requires parsing a list of ticket ID and status pairs. The Skill orchestrates the lifecycle transition by applying per-ticket mechanics inline before committing the batch.

Can I automate ITIL ticket management by applying transition mechanics inline?

Yes, you can automate ITIL ticket management by providing multiple ticket-status pairs. The Skill applies transition mechanics inline, including file renaming and metadata edits, to orchestrate a complete batch update.

Does the batch transition tool validate each ticket before committing?

Yes, the batch transition tool enforces safety with per-pair validations and pre-flight checks. It detects external root causes and supports interactive prompts for upstream decisions before staging and committing the single batch.

How do I handle git-mv operations for ITIL docs and problems during a batch update?

To handle git-mv operations for ITIL docs and problems, the Skill automatically renames files and re-stages them during the batch transition. It parses the status pairs, applies the mechanics, and executes a single final commit.