incident-to-doc

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.