incident-team

Dispatch parallel investigation agents to analyze production incidents.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/mykaarma/claude-sutras --skill incident-team
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: incident-team
Source: https://github.com/mykaarma/claude-sutras/tree/main/skills/incident-team
Command: npx skills add https://github.com/mykaarma/claude-sutras --skill incident-team

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Incident investigations are often slow because they are performed sequentially, causing delays in root cause identification and mitigation during critical outages.

Core Features & Use Cases

  • Parallel Agent Dispatch: Simultaneously runs timeline building, root cause analysis, impact assessment, and mitigation finding agents.
  • Synthesis into Incident Brief: Combines agent outputs into a concise brief with recommended actions and mitigation options.
  • Use Cases: Ideal for P1/P2 production incidents, data integrity problems, or security events where the cause, impact, and fix are unknown.

Quick Start

Prompt the incident-team skill with the affected service, symptom description, and any available logs or Jira ticket to start the parallel investigation.

Frequently Asked Questions about incident-team

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

FAQPage Schema
How do I investigate a P1 production incident when the root cause and impact are unknown?

To investigate a P1 production incident with unknown root cause, dispatch parallel investigation agents to simultaneously analyze timeline, impact, and mitigation, synthesizing the results into a concise incident brief with recommended actions.

What is the best way to speed up root cause analysis during a critical outage?

The best way to speed up root cause analysis during an outage is parallel agent dispatch, which runs timeline building, impact assessment, and mitigation finding concurrently rather than sequentially to identify fixes rapidly.

How does parallel incident response work for data integrity or security events?

Parallel incident response for data integrity or security events works by simultaneously dispatching multiple agents to assess impact, build timelines, and analyze root causes, combining their outputs into a unified mitigation recommendation.

Do I need a Jira ticket to start an incident investigation?

You do not need a Jira ticket to start an incident investigation; it is optional. You must provide incident context like affected services, symptoms, and timestamps to coordinate the parallel investigation and mitigation analysis.

When should I use parallel incident investigation instead of sequential troubleshooting?

Use parallel incident investigation instead of sequential troubleshooting for P1 or P2 production incidents, data integrity problems, or security events where cause, impact, and mitigation are unknown and rapid fixes are critical.