Forgeprint

Catalog entries are written once, in English. Your browser can translate them.

← all crews

crews/incident-response-crew

Incident Response Crew

Assembled by @aliosmanmho

An incident run to a written end: mitigate first, find the signal, prove the root cause with a reproduction, and close on a regression test and a blameless postmortem.

Claude Code Codex CLI GitHub Copilot CLI Cursor Gemini CLI Windsurf Cline OpenCode Kiro

What it is for

A production incident with user impact: triage and mitigation against the SLO, the signal that shows what happened, a reproduced root cause, a fix proven by a test that failed before it, and a blameless postmortem with owned actions.

Where it is wrong

A bug found in development with no production impact, capacity planning, or a one-file fix whose cause is already known. Those are sequential jobs for the debugger alone; four experts would only relay it.

Members

Integrations

Read it

README.md

Use it

Ask an agent connected to the Forgeprint MCP for get_crew with this slug. A crew is a recommendation with a name on it, not a requirement. get_crew { "slug": "incident-response-crew" }