incident-responder · qdhenry — Claude Code subagent: what it does
incident-responder guides production incident response, from assessing impact and coordinating roles to restoring service and documenting follow-up work.
no license ★ 1,357 updated 2026-03-01
.claude/agents/incident-responder.mdWhat incident-responder does
The subagent helps organize an incident response: classify severity from P0 to P3, identify affected services, and coordinate communication. For investigation, it directs attention to recent releases or configuration changes, then to logs, metrics, and traces. Possible stabilization steps include a rollback, adding capacity, disabling a feature, or shifting traffic.
Once service is stable, it can help record the event timeline, notify stakeholders, and prepare a blameless postmortem with assigned follow-up work. Its listed tools include file editing, Bash, web search, and the context7 and sequential-thinking integrations. Staging verification is recommended when feasible; the proposed rollout process also calls for a rollback plan.
What it helps with
- classify a production outage by severity and scope
- coordinate incident roles and response tasks
- compare telemetry with recent deployments or configuration changes
- choose a mitigation to stabilize an affected service
- draft a postmortem with owners for follow-up actions
Example prompts for the agent
- Help me assess this production incident and lay out the response steps.
- Coordinate recovery after the latest deployment and prepare a rollback plan.
- Draft a blameless postmortem from the incident timeline, with owners for follow-up tasks.
How to install incident-responder
Manually: put the files in place
.claude/agents/incident-responder.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/incident-responder.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/incident-responder.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about incident-responder
How do I install incident-responder in Claude Code?
Add the subagent file at .claude/agents/incident-responder.md.
What does incident-responder do?
It guides production incident response, including severity assessment, team coordination, service recovery, and post-incident review.
Which recovery options does it consider?
It can consider reverting a recent release, adding resources, turning off a problematic feature, or moving traffic to a healthy region or instance.
Similar subagents
All subagents for DevOps and infrastructure →incident-responder by other authors comes first.