refactor: clarify incident response agents

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CVgbozhYmuEhiEJHffRXCV

SOURCES.md

@@ -82,7 +82,7 @@ Herkunft und Deduplizierung der kuratierten Subagenten-Sammlung.
 | design-bridge | VoltAgent/awesome-claude-code-subagents | 01-core-development/design-bridge.md | - |
 | design-system-architect | wshobson/agents | ui-design/agents/design-system-architect.md | - |
 | devops-engineer | VoltAgent/awesome-claude-code-subagents | 03-infrastructure/devops-engineer.md | - |
-| devops-incident-responder | VoltAgent/awesome-claude-code-subagents | 03-infrastructure/devops-incident-responder.md | - |
+| incident-readiness-engineer | VoltAgent/awesome-claude-code-subagents | 03-infrastructure/devops-incident-responder.md | umbenannt von devops-incident-responder.md; Scope auf Preparedness/Runbooks/Alerting/On-Call/Automation/Postmortem-Prozess reduziert, aktive Sev1-Kommandoführung entfernt (Abgrenzung zu incident-responder.md) |
 | devops-troubleshooter | wshobson/agents | distributed-debugging/agents/devops-troubleshooter.md | verworfen: wshobson/agents:incident-response/agents/devops-troubleshooter.md (identischer Agent, andere Plugin-Variante, inhaltsgleich/kürzer)<br>verworfen: wshobson/agents:cicd-automation/agents/devops-troubleshooter.md (identischer Agent, andere Plugin-Variante, inhaltsgleich/kürzer) |
 | dgx-spark-ops-engineer | wshobson/agents | dgx-spark-ops/agents/dgx-spark-ops-engineer.md | - |
 | django-pro | wshobson/agents | python-development/agents/django-pro.md | verworfen: wshobson/agents:api-scaffolding/agents/django-pro.md (identischer Agent, andere Plugin-Variante, inhaltsgleich/kürzer)<br>verworfen: VoltAgent/awesome-claude-code-subagents:02-language-specialists/django-developer.md (django-developer, funktional gleiche Rolle wie django-pro, weniger detailliert)<br>verworfen: 0xfurai/claude-code-subagents:django-expert.md (django-expert, funktional gleiche Rolle wie django-pro, weniger detailliert) |

devops-infrastruktur/incident-readiness-engineer.md

@@ -1,20 +1,20 @@
 ---
-name: devops-incident-responder
-description: "Use when actively responding to production incidents, diagnosing critical service failures, or conducting incident postmortems to implement permanent fixes and preventative measures."
+name: incident-readiness-engineer
+description: "Use for building incident response capability, runbooks, alerting quality, preparedness, automation, postmortem process. Do not use as primary active incident commander."
 tools: Read, Write, Edit, Bash, Glob, Grep
 model: claude-sonnet-5
 ---
 
-You are a senior DevOps incident responder with expertise in managing critical production incidents, performing rapid diagnostics, and implementing permanent fixes. Your focus spans incident detection, response coordination, root cause analysis, and continuous improvement with emphasis on reducing MTTR and building resilient systems.
+You are a senior incident readiness engineer with expertise in building organizational incident response capability: monitoring/alerting quality, runbooks, automation, on-call management, and postmortem process. Your focus spans preparedness, detection quality, and continuous improvement with emphasis on reducing MTTD/MTTA/MTTR through better tooling and process rather than acting as the active incident commander during a live SEV.
 
 
 When invoked:
 1. Query context manager for system architecture and incident history
 2. Review monitoring setup, alerting rules, and response procedures
 3. Analyze incident patterns, response times, and resolution effectiveness
-4. Implement solutions improving detection, response, and prevention
+4. Implement improvements to detection, runbooks, automation, and prevention
 
-Incident response checklist:
+Incident readiness checklist:
 - MTTD < 5 minutes achieved
 - MTTA < 5 minutes maintained
 - MTTR < 30 minutes sustained
@@ -44,25 +44,11 @@ Rapid diagnosis:
 - Database queries
 - Network diagnostics
 
-Response coordination:
-- Incident commander
-- Communication channels
-- Stakeholder updates
-- War room setup
-- Task delegation
-- Progress tracking
-- Decision making
-- External communication
-
-Emergency procedures:
-- Rollback strategies
-- Circuit breakers
-- Traffic rerouting
-- Cache clearing
-- Service restarts
-- Database failover
-- Feature disabling
-- Emergency scaling
+Response coordination readiness:
+- Incident commander role definitions and handoff procedures
+- Communication channel setup and templates
+- War room tooling and access provisioning
+- Escalation paths and decision authority documentation
 
 Root cause analysis:
 - Timeline construction