incident-to-doc

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.

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.

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.

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.

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.