skills.rest
windyroad
windyroadOFFICIAL
Explore all skills by this author →
WebsiteGitHub

wr-itil:transition-problem

Transition ITIL problem tickets through lifecycle states with ADR-014 compliant commits.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Open → Known Error → Verification Pending → Closed: transition ITIL problem tickets within a repository, ensuring consistent lifecycle progress and immutable audit trails.

Core Features & Use Cases

  • Validate the ticket exists, confirm the current status allows the requested transition, and perform pre-flight checks before any changes.
  • Rename the ticket file, update the Status field, append a Fix Released section when appropriate, re-stage changes, and refresh docs/problems/README.md in the same commit.
  • Maintain an auditable history with ADR-014 compliant commits and update the central README problem inventory.

Quick Start

Invoke the skill with a ticket ID and destination status, e.g., /wr-itil:transition-problem 042 known-error.

Frequently Asked Questions about wr-itil:transition-problem

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

FAQPage Schema
How do I transition an ITIL problem ticket to a known error status in git?▼

To transition an ITIL problem ticket, invoke the skill with the ticket ID and destination status. It executes inline transitions with pre-flight checks, root-cause detection for Open to Known Error, git mv, and ADR-014 compliant commits.

Can I move a problem ticket directly from Open to Closed without intermediate states?▼

No, you cannot skip states. The skill requires a valid current-to-destination transition path, enforcing the Open, Known Error, Verification Pending, and Closed lifecycle to ensure consistent progress and immutable audit trails.

How do I maintain an auditable history when updating problem ticket documentation?▼

Maintaining an auditable history involves ADR-014 compliant commits. The skill renames the ticket file, updates the Status field, appends a Fix Released section, and refreshes the central README problem inventory in the same commit.

What do I need to set up before advancing ITIL tickets through lifecycle stages in a repository?▼

You need an existing ticket file, a valid current-to-destination transition path, and repository access for file renaming, edits, and commits. The skill performs pre-flight checks to validate these requirements before any changes.

Related Skills

Explore More Software Engineering Skills→
windyroadwindyroad
4

wr-itil:close-incident

Validate linked problem terminal state and rename restored incident files to .closed.md.

Official
Advanced
JackSmack1971JackSmack1971

debug-root-cause-analysis

Guide structured root-cause debugging through observe, reproduce, hypothesize, test, fix, verify, and prevent phases.

Community
Advanced
xloxn69xloxn69
7

agileflow-adr

Convert discussed architectural decisions into MADR-formatted ADR files.

Community
Basic
windyroadwindyroad
4

wr-itil:reconcile-readme

Detect drift between README and ticket state, then apply narrative-preserving edits.

Official
Intermediate