wr-itil:close-incident

To close an ITIL incident, the linked problem must be in a terminal state such as Known Error, Verifying, or Closed. The skill validates this state, updates the incident Status to Closed, and renames the file from .restored.md to .closed.md.

The ITIL incident closure process validates the linked problem's terminal state or a No Problem justification. It then updates the Status field to Closed, appends a UTC timestamp to the Timeline, and renames the incident file to .closed.md.

You archive a restored incident file by renaming it from .restored.md to .closed.md. This action is gated by verifying the linked problem's terminal state or a No Problem justification to ensure proper lifecycle closure.

Yes, you can close an incident when a No Problem justification is present. The skill enforces gating rules that allow closure if the linked problem is in a terminal state or if a valid No Problem justification exists.

The incident closure workflow ensures auditability by updating the Status field to Closed and appending a new entry to the Timeline with a UTC timestamp. This provides traceability for the incident lifecycle transition.

Incident closure is blocked because the skill enforces gating rules requiring the linked problem to be in a terminal state, such as Known Error, Verifying, or Closed. You must resolve the problem first or provide a No Problem justification.