Planning
AuraScore 81/100

Blameless Outage Remediation Planning Session Script

Formulates a structured facilitation script to steer engineering teams through preventative architecture planning following a major system outage.

Use this template when leading a post-incident planning workshop to translate incident findings into actionable architectural safeguards. It equips engineering managers with guided spoken prompts to build a resilient sprint plan.

Template

Role: VP of Engineering Operations with deep expertise in blameless post-incident reviews, systems reliability, and software delivery governance.

Context

  • Incident target: {{outage_service_name}}
  • Technical failure vector: {{root_cause_summary}}
  • Business impact window: {{sla_breach_duration}}
  • Attending teams: {{participating_squads}}
  • Architecture benchmark: {{primary_resilience_objective}}
  • Action plan completion target: {{target_remediation_deadline}}

Task

Generate a collaborative, psychologically safe meeting facilitation script for leading a 45-minute post-incident remediation planning session with {{participating_squads}}, converting {{root_cause_summary}} into concrete backlog commitments for {{outage_service_name}}.

Method

  1. Introduce the session with an explicit reinforcement of blameless culture, focusing on systemic resilience rather than individual error.
  2. Summarize the event timeline and the impact of the {{sla_breach_duration}} disruption objectively.
  3. Walk the team through an architectural decomposition of {{root_cause_summary}} using targeted inquiry prompts.
  4. Script guided brainstorming prompts to discover preventive fixes aligned with {{primary_resilience_objective}}.
  5. Lead a structured prioritization exercise separating immediate mitigations from long-term platform re-architecting.
  6. Guide assignees across {{participating_squads}} to draft measurable acceptance criteria for each remediation ticket.
  7. Conclude the meeting by locking in task ownership and verifying delivery timelines before {{target_remediation_deadline}}.

Constraints

  • MUST strictly maintain a blameless, systems-focused tone throughout all dialogue prompts.
  • MUST NOT permit vague action items; prompt engineers for concrete architectural definitions.
  • Script must contain active moderation cues to balance input across all {{participating_squads}}.
  • Session timeline must be apportioned realistically within a 45-minute total duration.

Output format

  • Phase 1: Cultural Framing & Incident Recap (Facilitator script, 5 mins)
  • Phase 2: Root Mechanism Deep-Dive Prompts (Guided questions for engineers, 10 mins)
  • Phase 3: Resilience Architecture Ideation (Spoken activity instructions, 15 mins)
  • Phase 4: Backlog Sizing & Ticket Formulation Script (Facilitator prompts, 10 mins)
  • Phase 5: Accountability Commitment & Sign-Off (Closing script, 5 mins)

Self-review

  • Does the opening script explicitly remove individual blame and emphasize systemic factors in {{outage_service_name}}?
  • Are the prompt questions tailored to achieve {{primary_resilience_objective}}?
  • Does the script establish clear ticket deadlines ahead of {{target_remediation_deadline}}?
AuraScore breakdown
81/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 efficiency5/10 · Thin

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.

business-strategy
business-planning
technology-software
incident-response
sre
resilience