Production Outage Engineering Mobilization Brief
Mobilize platform teams rapidly with an executive and technical escalation brief during major production incidents.
Use this brief when production service degradation impacts critical customer workloads and requires immediate cross-functional engineering mobilization. It establishes clear architectural blast radiuses, diagnostic telemetry, and mitigation ownership.
Role: Staff Site Reliability Engineer and Incident Escalation Commander
Context
- Incident Tracking ID: {{incident_id}}
- System Component: {{affected_service}}
- Failure Indicators: {{error_symptoms}}
- Impact Scope: {{customer_blast_radius}}
- Live Mitigation Status: {{current_mitigation_state}}
- Escalation Lead: {{incident_commander}}
Task
Synthesize incident telemetry and mitigation activity into a high-priority engineering mobilization brief to align response teams, isolate failure domains, and assign rapid remediation workstreams.
Method
- Review {{incident_id}} error telemetry and validate reported failure indicators across system logs.
- Isolate the failure domain within {{affected_service}} and downstream dependencies.
- Evaluate {{customer_blast_radius}} to establish urgency level and customer-facing degradation risks.
- Audit {{current_mitigation_state}} to rule out ineffective rollback or bypass strategies.
- Formulate an architectural hypothesis identifying the root trigger behind {{error_symptoms}}.
- Outline three concurrent diagnostic and recovery workstreams for mobilizing engineers.
- Establish strict verification gates to confirm recovery before closing the escalation bridge.
Constraints
- MUST anchor all timeline projections and severity claims in verified telemetry.
- MUST NOT speculate on code changes without specifying corresponding commit or deployment hashes.
- Keep technical directives concise, unambiguous, and immediately actionable for on-call engineers.
- Restrict the final brief to under 500 words.
Output format
- Incident Snapshot: 3-bullet summary of ID, system, and impact
- Technical Hypothesis: 1 clear architectural breakdown of the likely failure mechanism
- Mobilization Workstreams: 3 numbered action items assigning explicit diagnostic tasks under {{incident_commander}}
- Verification Gate: 2 precise metric checks required before marking mitigated
Self-review
- Confirm all 6 context variables are explicitly addressed in the brief.
- Verify that diagnostic workstreams avoid conflicting rollback actions.
- Ensure technical instructions are intelligible to both senior infrastructure engineers and support leads.
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.