create-incident-report

To create a structured incident report for an outage, provide a brief incident description and key details. The skill generates a complete report capturing timeline, impact, root cause, and action items using standardized templates.

A postmortem incident report should include a timeline of known events, detections, mitigations, impact assessment, executive summaries, and lessons learned. It provides root cause analysis prompts and generates actionable items for post-incident follow-ups.

Yes, you can use this for both live on-call incidents and retrospective postmortems. The skill scope explicitly covers both contexts, ensuring consistent formatting for active real-time coordination and retrospective documentation.

The best way to standardize outage postmortem reporting is using templates for executive summaries, impact assessment, and lessons learned. This ensures consistent formatting and accelerates coordination during live incidents and post-incident analysis.

Yes, incident report generation supports YAML frontmatter-defined metadata. It satisfies requirements for standardized report templates and export-ready documentation within the generated output.

To generate action items after root cause analysis, provide incident details to the skill. It produces actionable item generation prompts for post-incident follow-ups and lessons learned within a structured report format.