General agents
AuraScore 79/100

Smart Grid Autonomous Dispatch Agent Pre-Commissioning Checklist

Verify autonomous grid balancing agents against SCADA telemetry, safety interlocks, and failover protocols prior to live dispatch.

Use this prompt when commissioning an autonomous agent for grid load-shedding, substation switching, or frequency response. It generates a comprehensive pre-live verification checklist across telemetry, safety, and operational boundaries.

Template

Role: Senior Grid Automation Architect specializing in autonomous dispatch systems and substations.

Context

  • Utility Operator: {{utility_name}}
  • Operating Zone: {{grid_zone}}
  • Supervisory Protocol: {{scada_protocol}}
  • Inference Latency Budget: {{agent_decision_latency}}
  • Redundancy Layer: {{failover_system}}
  • Regulatory Standard: {{regulatory_body}}

Task

Produce a technical pre-commissioning readiness checklist to evaluate an autonomous dispatch agent before granting live closed-loop control over grid switching and voltage regulation assets.

Method

  1. Establish boundary parameters by evaluating {{grid_zone}} physical limits and substation ratings.
  2. Review agent interface requirements across {{scada_protocol}} communication channels, verifying checksums and packet loss thresholds.
  3. Formulate telemetry validation items checking that state estimation algorithms accurately handle dirty or delayed sensor inputs.
  4. Design control action checks ensuring switching recommendations adhere to {{agent_decision_latency}} constraints without oscillation.
  5. Detail protection coordination items verifying autonomous logic yields to hardwired safety interlocks and {{failover_system}}.
  6. Specify audit logging checks to capture full decision traces required by {{regulatory_body}}.
  7. Structure verification gates for cold start, operational steady-state, emergency ramp-down, and disconnected network modes.

Constraints

  • Must organize checks chronologically from network isolation testing to live closed-loop gating.
  • MUST explicitly flag every high-voltage safety interlock check with a mandatory blocker status.
  • MUST NOT permit ambiguous verification criteria (every item must define pass/fail metric or source of truth).
  • Tailor terminology strictly to power systems engineering and SCADA communication.

Output format

  • Phase 1: Telemetry & Ingestion Checks (4-6 checklist items)
  • Phase 2: Algorithmic Inference & Latency Checks (4-6 checklist items)
  • Phase 3: Interlock, Safety & Failover Checks (5-7 checklist items)
  • Phase 4: Compliance & Blackbox Logging Checks (3-5 checklist items)
  • Sign-off Protocol Table with fields: Check ID, Verification Item, Acceptance Metric, Responsible Role, Blocker (Yes/No)

Self-review

  • Confirm every checklist item includes an unambiguous pass/fail condition.
  • Check that all variables including {{scada_protocol}} and {{failover_system}} are contextualized.
  • Ensure the format adheres strictly to standard checklist markdown syntax.
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 engineering10/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 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.

ai-agents
agents-general
energy-utilities
smart-grid
power-utilities
scada