incident-to-doc

Convert resolved IT incident summaries into structured Confluence post-mortems or runbook updates.

Updated Aug 27, 2026

Search Tags:#post-mortem #confluence #incident management #it operations #runbook update #atlassian mcp

Ready to run

npx skills add https://github.com/afoxnyc3/chelsea-piers-itops --skill incident-to-doc

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: incident-to-doc
Source: https://github.com/afoxnyc3/chelsea-piers-itops/tree/main/plugins/confluence-docs/skills/incident-to-doc
Command: npx skills add https://github.com/afoxnyc3/chelsea-piers-itops --skill incident-to-doc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the manual, error-prone work of turning resolved incidents into consistent Confluence post-mortems or runbook updates.

Core Features & Use Cases

Duplicate-safe documentation: Searches Confluence for an existing post-mortem tied to the incident ID to avoid creating duplicates.
Structured post-mortems: Generates a blameless, template-based page including timeline, root cause, resolution, impact placeholders, action items, and a change log.
Runbook maintenance: Updates an existing related runbook or creates a new one when needed.

For example, when a Jira incident is resolved, you can automatically produce a post-mortem page (or update a runbook) in the correct Confluence space with all required sections.

Quick Start

Convert the resolved incident INC-1042 into a Confluence post-mortem by providing the incident title, type, and summary to the incident-to-doc skill.

Frequently Asked Questions about incident-to-doc

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

FAQPage Schema

How do I create a Confluence post-mortem from a resolved incident automatically?▼

To create a Confluence post-mortem from a resolved incident, provide the incident title, type, and summary to generate a structured, blameless documentation page. The skill applies a template with timeline, root cause, resolution, and action items sections.

How does incident documentation handle duplicate post-mortems in Confluence?▼

Incident documentation prevents duplicate post-mortems by searching Confluence for an existing page tied to the specific incident ID before generating a new one. If a page exists, it avoids creating a duplicate entry.

Can I use this to update a runbook after an IT operations incident is resolved?▼

Yes, you can update an existing related runbook or create a new one after an IT operations incident is resolved. The process evaluates the incident summary and applies changes to the relevant runbook documentation.

What is included in a structured post-mortem generated from a resolved incident?▼

A structured post-mortem generated from a resolved incident includes a timeline, root cause, resolution, impact placeholders, action items, and a change log. It enforces blameless language to ensure objective documentation.

Does incident-to-doc work with Jira and PagerDuty incident inputs?▼

Yes, incident-to-doc works with Jira, PagerDuty, and free-text incident inputs. It processes the incident summary from these sources to trigger the documentation workflow when an incident is resolved.