mm-incident

Generate structured incident postmortems with root causes and action items.

1|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/mikkeymoo/claude-solo --skill mm-incident
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mm-incident
Source: https://github.com/mikkeymoo/claude-solo/tree/main/mm-skills/mm-incident
Command: npx skills add https://github.com/mikkeymoo/claude-solo --skill mm-incident

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill automates the creation of postmortems from incidents, streamlining the process of documenting incidents, their root causes, and preventing recurrence.

Core Features & Use Cases

  • Automated Incident Documentation: Generate structured incident reports that are ready to be filled in.
  • Customizable Timeline and Impact Analysis: Build a timeline of events and analyze the impact on users and services.
  • Root Cause and Prevention Insights: Facilitates understanding of the incident's root cause and potential prevention measures.
  • Quick Reference for Action Items: Ensures no task is overlooked by capturing action items for future consideration.
  • Use Case: Use /mm-incident to write a detailed postmortem after experiencing a service disruption.

Quick Start

Create a postmortem report for the "database outage on 2023-11-10" with the /mm-incident "database outage on 2023-11-10" command.

Frequently Asked Questions about mm-incident

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

FAQPage Schema
How do I create a postmortem report after an incident?

To create a postmortem report, provide a description of the incident to automatically generate structured documentation. This process captures the timeline, impact analysis, and root cause insights to prevent future occurrences.

What is the best way to document root causes for incident response?

Documenting root causes for incident response is best handled by automating the creation of detailed postmortems. This ensures structured output and easy tracking of root causes alongside actionable prevention measures.

Can I generate incident reports with a custom timeline and impact analysis?

You can generate incident reports featuring a customizable timeline and impact analysis. This allows you to build a detailed timeline of events and analyze the specific impact on users and services.

How do I track action items after a service disruption?

Track action items after a service disruption by generating a postmortem that captures tasks for future consideration. This ensures no task is overlooked by providing a quick reference for follow-up actions.

Does this postmortem tool require any specific dependencies to run?

This postmortem tool does not require any specific dependencies to run. It operates independently to automate the creation of incident documentation from a provided description of the event.

When do I need to use an automated incident documentation tool?

You need an automated incident documentation tool when you want to streamline the process of writing detailed postmortems after experiencing a service disruption. It helps organizations systematically analyze and prevent similar incidents.