Planning
AuraScore 81/100

Production Cutover War Room Facilitator Script

Generates a time-stamped live facilitation and command script for leading high-risk software cutovers and platform migrations.

Use this template when planning a live infrastructure or application cutover that requires strict orchestration across engineering disciplines. It outputs an actionable war room verbal script complete with go/no-go milestones and rollback protocols.

Template

Role: Principal Site Reliability Architect with fifteen years of experience leading mission-critical cloud migrations and distributed systems cutovers.

Context

  • Target application: {{system_name}}
  • Destination environment: {{target_infrastructure}}
  • Allotted cutover window: {{maintenance_window_hours}} hours
  • Allowable service degradation: {{downtime_tolerance_minutes}} minutes
  • Bridge facilitator: {{lead_operator_role}}
  • Hard abort thresholds: {{rollback_trigger_conditions}}

Task

Compose an authoritative, time-sequenced war room facilitation script that {{lead_operator_role}} will read aloud to orchestrate engineers during the cutover of {{system_name}} to {{target_infrastructure}}, ensuring safe deployment within {{maintenance_window_hours}} hours.

Method

  1. Establish the pre-flight roll call script, verifying telemetry, operational sign-offs, and communication bridge readiness.
  2. Script the formal Go/No-Go confirmation sequence across engineering leads before traffic manipulation.
  3. Detail the spoken command sequence for initiating traffic drain, data synchronization, and DNS redirection.
  4. Write the mid-cutover verification checkpoint, instructing the team to evaluate latency and error rate metrics against baseline targets.
  5. Draft explicit verbal decision branches: path A for successful validation and path B for immediate rollback under {{rollback_trigger_conditions}}.
  6. Structure the abort protocol script, defining exact vocal declarations to halt deployment and initiate rollback procedures.
  7. Provide the final all-clear wrap-up script, detailing customer notification handoffs and post-cutover monitoring assignments.

Constraints

  • MUST include explicit stage directions, speaker labels, and elapsed timeline markers (e.g., [T-00:15], [T+00:30]).
  • MUST NOT use ambiguous command phrasing; instructions must be direct, imperative, and verifiable.
  • Spoken lines must remain professional, concise, and calm under high-pressure scenarios.
  • Must respect the maximum downtime threshold of {{downtime_tolerance_minutes}} minutes in the rollback decision block.

Output format

  • Section 1: Pre-Flight Bridge Setup (Roll call dialogue and stage directions)
  • Section 2: Go/No-Go Decision Gate (Formal verbal polling template)
  • Section 3: Active Cutover Execution Script (Timed spoken instructions and confirmation responses)
  • Section 4: Abort & Rollback Script (Trigger response protocol)
  • Section 5: Stand-down & Sign-off Checklist Script (Closing debrief prompts) Total script length: 350 to 550 spoken words across sections.

Self-review

  • Does the script explicitly reference the {{rollback_trigger_conditions}} in the abort decision gate?
  • Are timeline markers aligned within the {{maintenance_window_hours}} hour boundary?
  • Can the facilitator read the script verbatim without needing to invent transition phrases?
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
devops
cutover
migration