incident-response-coordinator

ProfessionalRuntime top level

Use analysis-agent for active multi-responder incident command, cadence, mitigation, communications, or handoff. Skip ordinary diagnosis, reliability design, release approval, post-incident docs, and execution.

Group: Independent review, incident and routing governance
Routing mode: evidence-only
Supported roles: MainAnalysisTaskReview
Source: SKILL.md

Use when

Trigger signals that make this skill the right owner

Multiple responders or workstreams need one command structure.
Impact needs a shared severity and update cadence.
Diagnosis, mitigation, communications, and handoff need synchronization.

Do not use when

Anti-triggers — as binding as the triggers above

ordinary single-owner diagnosis without active coordination
reliability design or review without incident-command work
release or rollback approval
post-incident documentation after coordination is closed
Do not use this Skill to mutate production, deploy, execute a destructive action, or bypass operator authority.

Required inputs

What must be supplied before this skill can decide anything

current impact scope severity indicators and time basis
responder authority roles communication channels and decision cadence
known evidence hypotheses mitigations recovery signals and handoff constraints

Output contract

What this skill owes the next role

incident command record with severity roles cadence workstreams evidence and decision log
mitigation coordination authorization recovery verification communications and handoff record
proof limits unresolved risk owners and closure criteria

Escalation signals

When this skill must hand the decision back

command authority safety boundary destructive mitigation communication owner or recovery evidence remains unresolved

Related expertise

2 Layer 3 candidates may be loaded behind this skill. A single task loads at most three, and only when the current evidence justifies them.

Targeted references

Each reference carries its own load condition. None of them enter context by default.

Reference	Load when	Do not load when	Required by
command-cadence-and-decision-log.mdtargeted	Establishing command, cadence, workstreams, or the shared incident record	One owner is performing ordinary diagnosis or the incident is already closed	Analysis
mitigation-authorization-and-handoff.mdtargeted	Coordinating mitigation, recovery verification, closure, or transfer of command	The task is only diagnosis release approval reliability design or post-incident documentation	Analysis