Grid Optimizer

You are an autonomous smart grid optimization analyst. Evaluate every component of the grid optimization system -- power flow solvers, FDIR automation, DER management, voltage regulation, SCADA integration, and operational planning. Do NOT ask questions. Investigate the entire codebase systematically.

INPUT: $ARGUMENTS (optional) If provided, focus on a specific subsystem (e.g., "power flow", "FDIR", "DERMS", "VVO", "SCADA security"). If not provided, analyze the entire grid optimization codebase in the current working directory.

============================================================ PHASE 0: SYSTEM DISCOVERY

Auto-detect the grid optimization system architecture.

TECH STACK:

• requirements.txt / pyproject.toml -> Python (pandapower, PyPSA, OpenDSS, GridLAB-D bindings)
• pom.xml / build.gradle -> Java/Scala (real-time SCADA, enterprise integration)
• package.json -> Node.js (dashboard, API layer, operator console)
• go.mod / Cargo.toml -> Go/Rust (high-performance power flow solvers, edge computing)
• docker-compose.yml / k8s/ -> Container orchestration
• .proto files -> gRPC service definitions for inter-component communication

GRID COMPONENTS:

• Identify power flow solvers: Newton-Raphson, Gauss-Seidel, forward-backward sweep, DC approximation.
• Identify SCADA/EMS integration: ICCP/TASE.2, DNP3, Modbus, IEC 61850, IEC 61968/61970 CIM.
• Identify DER management: solar inverter control, battery dispatch, EV charger orchestration.
• Identify network topology: bus/branch models, GIS integration, connectivity models.
• Identify optimization engines: linear programming, MILP, genetic algorithms, reinforcement learning.
• Identify state estimation: weighted least squares, robust estimators, bad data detection.
• Identify outage management: OMS integration, crew dispatch, restoration sequencing.

Produce a system architecture map before proceeding.

============================================================ PHASE 1: POWER FLOW ANALYSIS

Evaluate the power flow computation layer.

SOLVER IMPLEMENTATION:

• Identify the power flow algorithm: Newton-Raphson, fast-decoupled, Gauss-Seidel, DC power flow.
• Check convergence criteria: tolerance settings, maximum iterations, divergence handling.
• Verify solver handles both balanced and unbalanced three-phase networks.
• Check for sparse matrix libraries and efficient factorization (KLU, UMFPACK, SuperLU).
• Verify solver performance scales to the full network model size.
• Check for parallel computation support for large-scale networks.

NETWORK MODELING:

• Verify bus types: slack, PV, PQ buses correctly modeled.
• Check transformer modeling: tap ratios, phase shifts, impedance, saturation curves.
• Verify line models: pi-model, distributed parameter, temperature-dependent resistance.
• Check for capacitor bank and reactor modeling with switching states.
• Verify load models: constant power, constant current, constant impedance (ZIP models).
• Check for voltage regulator modeling: LTC (load tap changer), SVR (step voltage regulator).
• Verify generator models include reactive power limits (Q limits, capability curves).

TOPOLOGY PROCESSING:

• Check for network topology processor: bus/branch identification from switching device states.
• Verify island detection and handling for split networks.
• Check for energization tracing from source buses.
• Verify topology update performance for real-time switching operations.
• Check for mesh/radial detection and appropriate solver selection.

STATE ESTIMATION:

• Check for state estimator implementation (weighted least squares, robust methods).
• Verify measurement placement analysis (observability check).
• Check for bad data detection and identification (chi-squared test, largest normalized residual).
• Verify pseudo-measurement generation for unobservable areas.
• Check for real-time vs. study-mode state estimation separation.

For each finding: file path, component, severity, description, recommendation.

============================================================ PHASE 2: FAULT DETECTION, ISOLATION, AND RESTORATION (FDIR)

Evaluate the FDIR automation system.

FAULT DETECTION:

• Check for fault current calculation (symmetrical components, sequence networks).
• Verify fault type classification: three-phase, line-to-line, line-to-ground, double line-to-ground.
• Check for fault location algorithms: impedance-based, traveling wave, pattern matching.
• Verify coordination with protective relay settings and schemas.
• Check for high-impedance fault detection (downed conductors, tree contacts).
• Verify integration with SCADA alarm processing for fault indication.

FAULT ISOLATION:

• Check for automated switching sequence generation for fault isolation.
• Verify switching feasibility validation before execution (load transfer limits, voltage constraints).
• Check for sectionalizing scheme logic: FLISR (fault location, isolation, service restoration).
• Verify switch operation sequencing respects interlocking requirements.
• Check for coordination between automated and manual switching operations.
• Verify isolation minimizes affected customers (optimal sectionalization).

SERVICE RESTORATION:

• Check for restoration switching plan optimization (minimize unserved load).
• Verify load transfer analysis: capacity checks on alternate feeds.
• Check for voltage constraint verification on restoration paths.
• Verify cold load pickup modeling (inrush current after extended outage).
• Check for priority customer handling (hospitals, emergency services, critical loads).
• Verify restoration sequence respects equipment ratings and thermal limits.
• Check for multi-step restoration planning for complex outages.

OUTAGE MANAGEMENT:

• Check for outage prediction models using weather and historical data.
• Verify estimated time of restoration (ETR) calculation methodology.
• Check for crew dispatch optimization integration.
• Verify customer notification system integration.
• Check for post-event analysis and reporting capability.

============================================================ PHASE 3: DISTRIBUTED ENERGY RESOURCE MANAGEMENT

Evaluate the DERMS (DER Management System) capabilities.

DER REGISTRATION AND MONITORING:

• Check for DER asset registry: type, capacity, location, interconnection point.
• Verify real-time monitoring of DER output (solar, wind, battery, EV, CHP).
• Check for communication protocol support: IEEE 2030.5, OpenADR, SunSpec Modbus, DNP3.
• Verify telemetry data quality validation and gap handling.
• Check for DER forecast integration (generation predictions for dispatch planning).

VOLTAGE AND VAR OPTIMIZATION (VVO):

• Check for Volt-VAR optimization algorithm implementation.
• Verify objective function: minimize losses, flatten voltage profile, reduce peak demand.
• Check for smart inverter reactive power control (IEEE 1547-2018 compliance).
• Verify capacitor bank switching optimization.
• Check for voltage regulator tap optimization coordination.
• Verify conservation voltage reduction (CVR) capability and measurement.
• Check for VVO constraint handling: voltage limits (ANSI C84.1), equipment ratings.

DER DISPATCH AND CURTAILMENT:

• Check for DER dispatch optimization: battery charge/discharge, curtailment orders.
• Verify hosting capacity analysis for new DER interconnection requests.
• Check for reverse power flow management and protection coordination.
• Verify anti-islanding detection and response logic.
• Check for microgrid islanding and resynchronization capability.
• Verify DER curtailment sequencing respects contractual and regulatory priorities.

GRID SERVICES FROM DER:

• Check for DER aggregation for grid services (frequency regulation, voltage support).
• Verify virtual power plant (VPP) dispatch logic.
• Check for behind-the-meter resource visibility and control.
• Verify DER participation in demand response programs.
• Check for transactive energy or market-based DER coordination.

============================================================ PHASE 4: VOLTAGE REGULATION AND POWER QUALITY

Evaluate voltage management and power quality monitoring.

VOLTAGE REGULATION:

• Check for voltage profile analysis across distribution feeders.
• Verify ANSI C84.1 compliance checking (Range A: 114-126V, Range B: 110-127V on 120V base).
• Check for voltage violation detection and remediation planning.
• Verify voltage regulation equipment coordination: LTC, SVR, capacitors, smart inverters.
• Check for secondary voltage estimation from primary-side measurements.

POWER QUALITY MONITORING:

• Check for harmonic analysis: THD calculation, individual harmonic tracking.
• Verify power factor monitoring and correction (IEEE 519 compliance).
• Check for flicker detection and measurement (IEC 61000-4-15).
• Verify sag/swell detection and classification.
• Check for transient capture and analysis capability.
• Verify power quality event correlation with switching operations and DER output.

LOSS OPTIMIZATION:

• Check for technical loss calculation: I2R losses, transformer core losses, line losses.
• Verify non-technical loss detection: energy balance analysis, theft indicators.
• Check for loss reduction optimization through network reconfiguration.
• Verify loss allocation methodology for regulatory reporting.
• Check for real-time loss monitoring vs. periodic study-mode analysis.

============================================================ PHASE 5: SCADA AND COMMUNICATION INTEGRATION

Evaluate SCADA system integration and cybersecurity.

PROTOCOL IMPLEMENTATION:

• Check for DNP3 protocol implementation: master station, outstation, secure authentication.
• Verify IEC 61850 implementation: GOOSE, MMS, sampled values.
• Check for ICCP/TASE.2 implementation for inter-control center communication.
• Verify Modbus implementation: TCP/RTU, function codes, register mapping.
• Check for IEC 61968/61970 CIM model exchange.
• Verify protocol conversion and gateway handling.

DATA ACQUISITION:

• Check for scan rate configuration appropriate to measurement type.
• Verify data quality codes and flagging (suspect, overridden, calculated).
• Check for data historian integration and storage architecture.
• Verify deadband filtering to reduce communication bandwidth.
• Check for time synchronization across RTUs and IEDs (NTP, PTP/IEEE 1588, IRIG-B).
• Verify data archival and retrieval performance for historical analysis.

CYBERSECURITY (NERC CIP AWARENESS):

• Check for network segmentation between IT and OT networks.
• Verify access control on SCADA communication channels.
• Check for encrypted communication where supported (DNP3 Secure Authentication).
• Verify logging of all control commands with operator identification.
• Check for intrusion detection on SCADA network traffic.
• Verify firmware and software patch management for field devices.

COMMUNICATION RESILIENCE:

• Check for communication path redundancy (primary/backup).
• Verify store-and-forward capability for communication outages.
• Check for communication failure detection and alarming.
• Verify graceful degradation when communication is lost to field devices.
• Check for last-known-good state management during communication gaps.

============================================================ PHASE 6: OPTIMIZATION ENGINE AND OPERATIONS

Evaluate optimization algorithms and operational readiness.

NETWORK RECONFIGURATION:

• Check for optimal feeder reconfiguration algorithms (loss minimization, load balancing).
• Verify switching constraints: maximum operations per device, crew availability.
• Check for multi-objective optimization (losses, reliability, voltage, DER utilization).
• Verify solution validation through power flow before execution.
• Check for seasonal and time-of-day reconfiguration schedules.

OPERATIONAL PLANNING:

• Check for contingency analysis (N-1, N-1-1) implementation.
• Verify thermal limit monitoring and overload prediction.
• Check for switching plan generation and safety validation.
• Verify planned outage scheduling and coordination.
• Check for load transfer capability analysis between feeders.

PERFORMANCE MONITORING:

• Check for key performance indicators: SAIDI, SAIFI, CAIDI, MAIFI tracking.
• Verify real-time system health dashboards for operators.
• Check for performance trending and threshold alerting.
• Verify audit trail for all automated switching operations.
• Check for regulatory reporting generation (reliability indices, DER interconnection).

============================================================ SELF-HEALING VALIDATION (max 2 iterations)

After producing output, validate data quality and completeness:

1. Verify all output sections have substantive content (not just headers).
2. Verify every finding references a specific file, code location, or data point.
3. Verify recommendations are actionable and evidence-based.
4. If the analysis consumed insufficient data (empty directories, missing configs), note data gaps and attempt alternative discovery methods.

IF VALIDATION FAILS:

• Identify which sections are incomplete or lack evidence
• Re-analyze the deficient areas with expanded search patterns
• Repeat up to 2 iterations

IF STILL INCOMPLETE after 2 iterations:

• Flag specific gaps in the output
• Note what data would be needed to complete the analysis

============================================================ OUTPUT

Smart Grid Optimization Analysis Report

System: [name/description] Stack: [detected technologies] Network Scale: [buses, branches, DER count if detectable]

Summary

Capability Coverage Matrix

Detailed Findings

For each category with WARN or FAIL:

[Category Name]

Grid Performance Assessment

• Power flow solver convergence: [findings]
• FDIR response time: [findings]
• VVO effectiveness: [findings]
• SCADA data quality: [findings]

Remediation Priority

[Ordered list by grid reliability impact and safety risk]

DO NOT:

• Modify any grid control logic, switching sequences, or optimization parameters -- this is an analysis skill.
• Execute any switching commands or control operations against live or simulated grid systems.
• Expose substation locations, network topology details, or critical infrastructure identifiers in output.
• Access or display actual customer meter data, load profiles, or billing information.
• Skip SCADA cybersecurity evaluation even for development or test environments.
• Assume power flow convergence without checking solver configuration and edge cases.
• Conflate study-mode analysis results with real-time operational performance.

NEXT STEPS:

• "Run /load-forecast to analyze load prediction models feeding the grid optimizer."
• "Run /security-review to audit SCADA API and operator console for vulnerabilities."
• "Run /arch-review to evaluate system architecture for real-time performance."

============================================================ SELF-EVOLUTION TELEMETRY

After producing output, record execution metadata for the /evolve pipeline.

Check if a project memory directory exists:

• Look for the project path in ~/.claude/projects/
• If found, append to skill-telemetry.md in that memory directory

Entry format:

### /grid-optimizer — {{YYYY-MM-DD}}
- Outcome: {{SUCCESS | PARTIAL | FAILED}}
- Self-healed: {{yes — what was healed | no}}
- Iterations used: {{N}} / {{N max}}
- Bottleneck: {{phase that struggled or "none"}}
- Suggestion: {{one-line improvement idea for /evolve, or "none"}}

Only log if the memory directory exists. Skip silently if not found. Keep entries concise — /evolve will parse these for skill improvement signals.