wr-itil:restore-incident

Restore mitigating incidents to restored status and hand off to problem management.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Restores a mitigating incident to restored status and initiates a problem-management handoff to capture root-cause information, preserving audit trails and ensuring proper escalation when a problem record is required.

Core Features & Use Cases

  • Transition a Mitigating incident (e.g., .mitigating.md) to Restored (.restored.md), updating the Status field and appending a Service restored event to the Timeline.
  • Trigger the root-cause handoff via /wr-itil:manage-problem and optionally record a No Problem justification, maintaining governance and traceability.
  • Validate pre-flight conditions, enforce idempotent re-invocation handling, and ensure exactly one of Linked Problem or No Problem sections exists after the work.

Quick Start

Provide an incident ID to initiate restoration and trigger the root-cause handoff workflow.

Frequently Asked Questions about wr-itil:restore-incident

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

FAQPage Schema
How do I restore an ITIL incident and hand it off to problem management?

To restore an ITIL incident, you provide an incident ID to transition a mitigating incident to restored status, which updates the status field, appends a service restored event to the Timeline, and triggers the root-cause handoff workflow.

What is the process for transitioning a mitigating incident to a restored status?

Transitioning a mitigating incident to restored status involves validating pre-flight conditions, updating the Status field from mitigating to restored, and appending a Service restored event to the incident Timeline.

When do I need to record a No Problem justification during incident restoration?

You record a No Problem justification during incident restoration when a root-cause handoff is triggered but no problem record is required, ensuring exactly one of Linked Problem or No Problem sections exists for governance.

Does incident restoration support idempotent re-invocation if the process is triggered multiple times?

Yes, incident restoration enforces idempotent re-invocation handling, ensuring that triggering the restoration process multiple times on the same incident does not create duplicate timeline events or corrupt the audit trail.

What pre-flight checks are required before restoring a mitigating incident?

Pre-flight checks for restoring a mitigating incident validate the incident state and ensure the target active incident exists under docs/incidents, enforcing governance before updating the Timeline and triggering problem-management handoff.