wr-itil:link-incident

Link an existing problem record to an incident file.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Attach an existing problem record to an incident by writing or updating the Linked Problem section in the incident file to reflect the problem's ID, title, and current status.

Core Features & Use Cases

  • Standalone link operation used after a problem was not attached during restore or when multiple incidents need linking; supports retroactive linking by replacing or adding the Linked Problem section and updating the incident's timeline.
  • Handles three cases: Case A (no Linked Problem or No Problem present) results in appending the Linked Problem; Case B (Linked Problem exists) updates the entry if changed; Case C (No Problem present) converts No Problem into Linked Problem and records a retroactive timeline entry.
  • Reads incident files from docs/incidents and problem files from docs/problems to extract titles and statuses and validates the existence before linking.

Quick Start

Run the skill with the incident ID and problem ID as arguments to create or update the Linked Problem entry, for example: /wr-itil:link-incident I007 P071.

Frequently Asked Questions about wr-itil:link-incident

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

FAQPage Schema
How do I link an incident to a problem record after it was missed during the initial workflow?

To link an incident to a problem retroactively, the skill updates the Linked Problem section in the incident file with the problem's ID, title, and status. It appends the missing entry and records a retroactive timeline change for auditability.

What happens if an incident already has a No Problem entry but I need to attach a problem to it?

When attaching a problem to an incident with a No Problem entry, the skill converts the entry into a Linked Problem section. It populates the problem details and adds a retroactive timeline entry to maintain a continuous audit trail.

Can I update an existing Linked Problem entry in an incident file if the problem status changes?

Yes, if a Linked Problem section already exists, the skill updates the entry with the new status if it has changed. It modifies the incident document in place and maintains the auditable timeline to reflect the update.

Do I need to manually look up problem titles and statuses before attaching them to an incident file?

No, you do not need to manually look up problem details. The skill reads problem files from the docs/problems directory to extract titles and statuses automatically, validating existence before writing the Linked Problem entry into the incident file.

What is the best way to maintain an auditable trail when attaching multiple incidents to a single problem?

The best way to maintain an auditable trail is using a standalone link operation that updates each incident file individually. The skill formats the Linked Problem entry and records timeline changes within each incident document for every attachment made.