Skip to content
Windy Road Agent Plugins

@windyroad/itil

Service management workflows for Claude Code and Codex.

Maturity: Experimental, as stated in the package README.

Repository reference version: 3.3.0. This is the version recorded in the source tree; verify your installed version before relying on a skill or behavior.

Install for Claude Code

Section titled “Install for Claude Code”
Terminal window
npx @windyroad/itil

Restart Claude Code after installation. Choose your runtime and installation scope.

Skills

Section titled “Skills”
  • capture-problem: Experimental. Record a problem during ongoing work, with its impact, job trace and index entry.
  • capture-rfc: Experimental. Add an RFC release row to a story map, connecting a problem to stories delivered together.
  • capture-story: Experimental. Record a delivery story with problem, job and story-map traces.
  • capture-story-map: Experimental. Draft a story map connecting a problem and desired outcomes to coordinated delivery.
  • check-upstream-responses: Experimental. Poll upstream issues and pull requests we’ve filed via /wr-itil:report-upstream and surface new comments or reviews, state changes, or label changes since last check.
  • close-incident: Experimental. Close a restored incident after checking the linked problem’s status or a documented justification for having no linked problem.
  • link-incident: Experimental. Link an incident to an existing problem and record that problem’s current status.
  • list-incidents: Experimental. List active incidents from docs/incidents/ sorted by severity.
  • list-problems: Experimental. List open and known-error problems ordered by weighted priority.
  • list-stories: Experimental. List delivery stories and their status as a Markdown table.
  • list-story-maps: Experimental. List story-map artefacts from docs/story-maps/ as a markdown table.
  • manage-incident: Experimental. Declare, triage, mitigate, and close an incident using an evidence-first workflow.
  • manage-problem: Alpha. Create, update and prioritise problems using their impact, likelihood and estimated effort.
  • manage-rfc: Experimental. Manage a problem-traced release row and its delivery stories.
  • manage-story: Experimental. Create, refine and advance a delivery story through its lifecycle.
  • manage-story-map: Experimental. Create, refine and manage a story map for coordinated delivery.
  • migrate-story-map: Experimental. Replace an eligible legacy story map using a complete mapping approved by the adopter.
  • mitigate-incident: Experimental. Record a mitigation attempt against an incident — transitions an investigating incident to mitigating on the first attempt, appends subsequent attempts to the Mitigation attempts timeline.
  • outcome-led-planning: Experimental. Compatibility entrypoint for outcome-led planning, including optional GitHub coordination. Existing ITIL installations remain usable.
  • reconcile-readme: Experimental. Detect and correct drift between the problem index and its on-disk inventory.
  • reconcile-stories: Experimental. Detect and correct drift between docs/stories/README.md and the on-disk story inventory.
  • reconcile-story-maps: Experimental. Detect and correct drift between docs/story-maps/README.md and the on-disk story-map HTML inventory.
  • report-upstream: Experimental. Report a local problem ticket as a structured issue against an upstream repository, with bidirectional cross-references and SECURITY.md-aware routing for security-classified tickets.
  • restore-incident: Experimental. Record observed service restoration and hand the underlying cause to problem management.
  • review-problems: Experimental. Reassess open and known-error problems, their risks, effort and priority.
  • scaffold-intake: Experimental. Scaffold the four OSS intake surfaces (.github/ISSUE_TEMPLATE/, SECURITY.md, SUPPORT.md, CONTRIBUTING.md) for a downstream project that adopts @windyroad/itil.
  • transition-problem: Experimental. Advance a problem ticket’s lifecycle status — Open → Known Error, Open or Known Error → Verification Pending (verifying), Verification Pending → Closed.
  • transition-problems: Experimental. Batch-advance multiple problem tickets through the lifecycle in one invocation — Open → Known Error, Open or Known Error → Verification Pending, Verification Pending → Closed.
  • update-upstream: Experimental. Post a lifecycle-update comment to an upstream issue when a local problem ticket transitions.
  • work-problem: Experimental. Investigate and repair the highest-priority eligible problem, then follow the project’s delivery workflow.
  • work-problems: Experimental. Batch-work ITIL problem tickets while the user is AFK.

Package documentation

Section titled “Package documentation”

Read the package README on GitHub for configuration, dependencies and detailed behavior.

View @windyroad/itil on npm.