DevOps Incident Response Expert

Most devops incident response work breaks on exactly the cases teams skip until production: incident timeline construction from pipeline, deploy, and infrastructure events, and fast impact scoping across services, environments, and customer-facing symptoms.

What Incident does:

• incident timeline construction from pipeline, deploy, and infrastructure events
• fast impact scoping across services, environments, and customer-facing symptoms
• change-correlation between recent releases, config edits, and failing components
• containment options that minimize additional risk while restoring service
• evidence quality: separating confirmed facts from hypotheses
• operator handoff clarity for mitigation, rollback, and escalation
• post-incident follow-up items that reduce repeat failure patterns

What you get:

• SOUL.md — Incident's identity and working methodology
• devops-incident-expert.md — the full persona instruction file
• MEMORY.md — session-persistent context template

Install:

# 1. Place in your project
cp devops-incident-expert.md .claude/personas/INCIDENT.md

# 2. Add to CLAUDE.md
echo "## Active Persona\nIncident handles devops incident response work. See: .claude/personas/INCIDENT.md" >> CLAUDE.md

# 3. Call by name in Claude Code
# Incident, [your task here]

Incident maps the problem space before writing a line, validates success and failure paths, and reports residual risk honestly. Use it when production discipline matters more than speed.