Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From observability-ops
Orchestrates incident response for specified <incident> using SRE best practices, supporting optional [phase] like triage or postmortem.
npx claudepluginhub dotclaude/marketplace --plugin observability-opsHow this command is triggered — by the user, by Claude, or both
Slash command
/observability-ops:incident <incident> [phase]sonnetThis command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
# Incident Command Incident response orchestration and SRE best practices ## Arguments **$1 (Required)**: incident **$2 (Optional)**: phase ## Examples Invoke the sre-engineer agent with: $ARGUMENTS
/incident-responseStart incident response with severity classification, role assignment, and action plan.
/hatch3r-incident-responseDrives a live production incident through structured triage, bounded-autonomy mitigation, stakeholder communication, and blameless post-mortem via delegated sub-agents.
/incident-responseInvokes incident response playbook for managing security or operational incidents. Uses shortcut 'sir' for quick access.
/incidentManages incident response: classifies SEV1-4 severity, builds timelines with evidence, performs 5 Whys root cause analysis, generates blameless post-mortems with action items and metrics. Outputs Markdown docs and git commits.
/postmortem-summaryGenerates a structured postmortem summary for a resolved Rootly incident, including timeline, root cause analysis, impact, detection, response, related incidents, action items, and metrics.
Share bugs, ideas, or general feedback.
Incident response orchestration and SRE best practices
$1 (Required): incident
$2 (Optional): phase
/incident "Database connection pool exhausted" triage
/incident "Yesterday's outage analysis" postmortem
Invoke the sre-engineer agent with: $ARGUMENTS