Clients
AuraScore 83/100

Agent Workflow Failure Post-Mortem Communication Plan

Structure and compose executive client communications following autonomous chain loops or tool execution failures.

Use this template when an autonomous multi-step agent chain or tool integration suffers an outage, execution loop, or degraded accuracy. It creates a reassuring incident post-mortem email and remediation plan for client stakeholders.

Template

Role: Principal AI Reliability Director managing high-stakes enterprise autonomous agent deployments.

Context

  • Client Stakeholder: {{enterprise_client}}
  • Incident Summary: {{incident_summary}}
  • Impacted Agent Chain: {{affected_tool_chain}}
  • Identified Root Cause: {{root_cause_analysis}}
  • Technical Remediation: {{recovery_actions}}
  • SLA & Business Impact: {{sla_impact}}

Task

Generate an incident communication plan and executive-level resolution email that details the root cause of an autonomous agent execution failure, outlines remediation steps, and restores client trust.

Method

  1. Deconstruct {{incident_summary}} to isolate where tool selection, execution, or looping broke down.
  2. Map the failure sequence across {{affected_tool_chain}} to provide a clear timeline of events.
  3. Translate complex LLM or tool error modes into clear, business-appropriate language for {{enterprise_client}}.
  4. Present {{root_cause_analysis}} highlighting guardrail adjustments and deterministic safeguards.
  5. Detail the immediate {{recovery_actions}} taken to stabilize production agent chains.
  6. Address {{sla_impact}} transparently, specifying monitoring enhancements and circuit-breaker policies.
  7. Format the complete communication dispatch with clear executive summary and technical appendices.

Constraints

  • MUST clearly distinguish between model non-determinism, infrastructure outages, and schema validation errors.
  • MUST NOT shift blame to third-party model providers without articulating internal redundancy steps.
  • Language must maintain high accountability and technical rigor.
  • The email body must be under 450 words while technical appendices provide full context.

Output format

  • Executive Dispatch Plan: Stakeholder mapping and delivery timing
  • Client Incident Email: Executive Summary, Incident Timeline, Root Cause, Preventative Measures, SLA Next Steps
  • Action Item Matrix: Remediation task list with target completion dates

Self-review

  • Ensure the explanation of tool failure mechanisms is accessible to both CTOs and business leads.
  • Confirm that every remediation step directly targets a factor identified in the root cause.
  • Validate that all provided variables are contextualized correctly.
AuraScore breakdown
83/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency7/10 · Adequate

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

emails
emails-clients
autonomous-agents-workflows
incident-response
agentic-workflows
post-mortem