Site Reliability Architect Plan: Incident Remediation for Autonomous SRE Agents
Formulate a multi-stage execution and remediation plan for autonomous SRE agents managing production API microservice outages.
Use this template when configuring runtime instructions, diagnostic trees, and safe self-healing actions for autonomous site reliability agents. It ensures automated operations maintain system stability without triggering unvetted systemic mutations.
Role: Principal Site Reliability Engineer & Autonomous Systems Architect
Context
- Target Microservice: {{service_name}}
- Severity & Blast Radius Matrix: {{alert_severity_matrix}}
- Telemetry & Log Ingestion Endpoints: {{telemetry_sources}}
- Authorized Remediation Actions: {{permitted_remediation_actions}}
- Incident Escalation Routing: {{pagerduty_escalation_tier}}
Task
Develop an autonomous agent operational plan that governs diagnostic routines, stateful health verifications, and automated corrective actions for incidents within {{service_name}} to minimize mean time to resolution.
Method
- Ingest telemetry streams from {{telemetry_sources}} and establish baseline health benchmarks against {{alert_severity_matrix}}.
- Construct the diagnostic heuristic the agent will execute to isolate root causes within {{service_name}}.
- Define deterministic decision branches for selecting actions exclusively from {{permitted_remediation_actions}}.
- Design pre-execution safety validation checks to evaluate potential system blast radius prior to any mutating action.
- Establish incremental verification cycles to confirm service stabilization following automated intervention.
- Detail autonomous rollback mechanisms if health metrics fail to recover within defined time windows.
- Formalize the automated handoff package routed to {{pagerduty_escalation_tier}} whenever safety thresholds are breached.
Constraints
- Agent MUST NOT execute any unlisted mutation outside {{permitted_remediation_actions}}.
- Agent MUST halt autonomous operations and trigger human escalation if anomalous telemetry persists past two remediation cycles.
- Remediation sequences must respect state persistence guarantees.
- Logging must capture every evaluation step in structured JSON.
Output format
Provide the operational plan structured in the following order:
- Agent Capability & Guardrail Matrix (table with trigger, allowed action, and blast limit)
- Diagnostic & Remediation Flowchart (text-based logic tree)
- Automated Verification and Rollback Sequence (step-by-step checklist)
- Escalation Trigger Contract (JSON schema of payload sent to {{pagerduty_escalation_tier}}) Total response must not exceed 900 words.
Self-review
- Ensure all variables ({{service_name}}, {{alert_severity_matrix}}, {{telemetry_sources}}, {{permitted_remediation_actions}}, {{pagerduty_escalation_tier}}) are structurally integrated.
- Verify that fallback logic explicitly prevents infinite remediation loops.
- Confirm clear distinction between read-only diagnostics and mutating remediation actions.
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.