Scripts
AuraScore 79/100

Architecture Decision Record Deliberation Script

Create an interactive moderation and pitch script to facilitate high-stakes system design reviews and trade-off debates.

Deploy this template when leading architectural review board (ARB) sessions to debate competing design paradigms. It ensures balanced facilitation between contrasting infrastructure trade-offs, consensus building, and governance.

Template

Role: Principal Distributed Systems Architect and Technical Governance Lead

Context

  • Target subsystem: {{system_subsystem}}
  • Competing design proposals: {{competing_architectures}}
  • Critical system bottlenecks: {{performance_bottlenecks}}
  • Review board participants: {{stakeholder_roles}}
  • Availability and throughput targets: {{sla_requirements}}
  • Identified operational hazards: {{migration_risk_factors}}

Task

Generate a structured facilitation script and debate flow for a 45-minute Architecture Decision Record (ADR) review meeting that guides engineers to evaluate trade-offs and reach a defensible consensus.

Method

  1. Open the session by framing the architectural boundary conditions of {{system_subsystem}}.
  2. Summarize the latency, memory, and throughput bounds established in {{sla_requirements}}.
  3. Present the core trade-offs of the first approach from {{competing_architectures}} against {{performance_bottlenecks}}.
  4. Introduce the opposing approach from {{competing_architectures}}, contrasting cost, complexity, and scale.
  5. Guide structured inquiry rounds assigning specific critique prompts to {{stakeholder_roles}}.
  6. Walk through failover scenarios, rollback criteria, and mitigations for {{migration_risk_factors}}.
  7. Execute the formal consensus polling and document definitive ADR sign-off criteria.

Constraints

  • MUST allocate explicit time caps for each debate round.
  • MUST NOT favor any architecture without grounding arguments in {{sla_requirements}}.
  • Provide adversarial stress-test questions that challenge both architectural options.
  • Ensure clear transition cues between the moderator and designated stakeholder roles.

Output format

  • Section 1: Meeting Agenda & Moderation Rules (Pacing, Rules of Engagement)
  • Section 2: Facilitator Dialogue & Transition Script (Structured by minute markers with spoken prompts)
  • Section 3: Trade-Off Matrix & Decision Scorecard (Tabular template for live voting)

Self-review

  • Confirm that all participants in {{stakeholder_roles}} have distinct speaking prompts.
  • Verify that each risk in {{migration_risk_factors}} is assigned an explicit evaluation check.
  • Check that the debate script maintains strict neutrality between {{competing_architectures}}.
AuraScore breakdown
79/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 engineering8/12 · Adequate

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.

writing-content
writing-scripts
software-engineering-debugging
system-architecture
adr
technical-leadership