hms-commander

Codex-native adapter for invoking Anthropic Claude Code CLI as an independent read-only QAQC reviewer using markdown file handoff. Use when the user explicitly asks Codex to ask Claude, Claude Code, Opus, or Anthropic for a QAQC/code review, second-model review, or independent review. Do not trigger for generic QAQC unless the user asks for Claude specifically. Triggers: claude review, claude code review, ask claude, invoke claude, claude qaqc, opus review, anthropic review, second model with claude Prerequisites: Claude Code CLI authenticated and available as `claude`. Default model: opus with xhigh effort for deep reviews; use sonnet/high for faster or lower-cost review passes.

Claude-native adapter for invoking OpenAI Codex CLI through markdown handoff files. Use when Claude Code needs an explicit Codex QAQC review, Codex code review, cross-harness verification, implementation pass, refactoring pass, or second-model opinion. Default to read-only review unless the user explicitly asks Codex to edit files. Uses current `codex exec` commands, repository-local paths, and TASK.md/OUTPUT.md artifacts under `agent_tasks/handoffs/codex/`.

Clones HEC-HMS components (basins, met models, control specs, runs) using the CLB Engineering LLM Forward approach. Creates non-destructive, traceable, GUI-verifiable copies for QAQC comparison, scenario analysis, and parameter sensitivity testing. Use when creating alternative scenarios, setting up QAQC workflows, comparing baseline vs updated models, preserving originals while testing modifications, Atlas 14 precipitation updates (keep TP40 baseline), or model calibration with different parameter sets. All clones appear in HEC-HMS GUI with separate DSS outputs for side-by-side comparison. Trigger keywords: clone, duplicate, copy, QAQC, scenario, alternative, baseline, comparison, side-by-side, non-destructive, traceable.

Executes HEC-HMS simulations using HmsCmdr.compute_run(), handles parallel execution across multiple runs, and manages Jython script generation. Use when running HMS simulations, executing runs, computing models, setting up parallel computation workflows, generating Jython scripts, or running batch simulations. Handles HMS 3.x and 4.x version differences and Python 2/3 compatibility. Trigger keywords: run simulation, execute HMS, compute run, parallel execution, batch runs, Jython script, HMS compute, run model.

Exports HEC-HMS basin geometry and simulation results to cloud-native geospatial formats (GeoParquet, PMTiles) using the hms2cng package (HMS to Cloud Native GIS). Supports all HMS element types (subbasins, reaches, junctions, diversions, reservoirs, sources, sinks, watershed boundary) plus SQLite-based grid layers (subbasin polygons, flowpaths). Also exports results summary statistics (peak, min, mean) spatially joined with geometry. Use when generating GeoParquet for DuckDB/web analysis, PMTiles for map visualization, syncing to PostGIS, exporting basin elements for web GIS, building interactive map layers, or creating cloud-optimized archives of HMS project geometry. Trigger keywords: GeoParquet, PMTiles, cloud native, vector tiles, export geometry, export results, spatial export, parquet, tippecanoe, PostGIS sync, web map, DuckDB query, hms2cng.

Extracts and analyzes HEC-HMS simulation results from DSS files using HmsDss and HmsResults classes. Handles peak flows, hydrographs, volume summaries, and time series data. Leverages ras-commander's RasDss for DSS V6/V7 support. Use when processing HMS results, extracting peak flows, analyzing hydrographs, computing volumes, exporting time series, comparing multiple runs, or linking HMS results to HEC-RAS boundary conditions. Trigger keywords: DSS file, results, peak flow, hydrograph, time series, volume, extract results, HMS output, analyze results, compare runs.

Investigates HEC-HMS internals through decompiled Java classes. Provides JythonHms API reference, CLI options, version-specific differences (3.x vs 4.x), and guides on-demand decompilation for new discoveries. Use when debugging HMS behavior, discovering undocumented features, understanding version differences, validating automation approaches, checking JythonHms method signatures, or investigating HMS API capabilities. Complements hms_query_docs (official docs) with internal implementation details. Do NOT use for: official documentation queries (use hms_query_docs), hms-commander API questions (read code docstrings), or project file parsing (use hms_parse_basin-models). Trigger keywords: decompile, HMS internals, JythonHms API, HMS version differences, CLI options, undocumented, HMS jar, debugging HMS, HMS source code, method signatures.

Links HEC-HMS watershed models to HEC-RAS river models by extracting HMS DSS results and preparing them for RAS boundary condition import. Handles flow hydrograph export, spatial referencing (HMS outlets to RAS cross sections), DSS pathname formatting, quality validation, and time series alignment. Use when setting up HMS-to-RAS workflows, exporting HMS results for RAS, preparing upstream boundary conditions, coordinating watershed-to-river integrated modeling, or validating HMS results before handoff. Leverages shared RasDss infrastructure for consistent DSS operations across both tools. Trigger keywords: HMS to RAS, link HMS RAS, boundary condition, upstream BC, watershed to river, integrated model, export HMS, spatial matching, hydrograph import.

Manages HEC-HMS version differences (3.x vs 4.x), handles Python 2/3 compatibility, detects HMS installations, and generates version-appropriate Jython scripts. Use when working with legacy HMS 3.x projects, upgrading models from 3.x to 4.x, testing across multiple HMS versions, troubleshooting version-specific issues, or understanding 32-bit vs 64-bit architecture differences and memory limits. Trigger keywords: HMS version, HMS 3.x, HMS 4.x, legacy, upgrade, Python 2 compatible, 32-bit, 64-bit, version detection, multi-version testing.

Parses HEC-HMS basin model files (.basin) to extract and modify subbasins, junctions, reaches, loss parameters, transform parameters, baseflow, and routing. Use when reading basin files, modifying hydrologic parameters, analyzing basin structure, updating curve numbers or lag times, bulk parameter updates via CSV, or setting up clone workflows. Handles all loss methods (Deficit & Constant, SCS CN, Green & Ampt), transform methods (SCS UH, Clark, ModClark), and routing methods (Muskingum, Lag, ModPuls). Trigger keywords: basin file, subbasin, junction, reach, loss method, curve number, transform, lag time, baseflow, routing, Muskingum, parse basin, get parameters, batch parameters, CSV export.

Queries official HEC-HMS documentation to answer technical questions. Provides access to User's Manual, Technical Reference Manual, Release Notes, and community resources. Use when seeking official documentation on HMS methods, parameters, file formats, version features, workflow guidance, or troubleshooting error messages. Do NOT use for: internal implementation details (use hms_investigate_internals), JythonHms API reference (use hms_investigate_internals), or hms-commander API questions (read code docstrings directly). Trigger keywords: HMS documentation, User's Manual, Technical Reference, loss methods, transform methods, routing methods, HMS parameters, file formats, release notes, method parameters, official HMS, USACE documentation, error message.

Updates HEC-HMS meteorologic model files (.met) including precipitation methods, gage assignments, evapotranspiration, and Atlas 14 frequency storms. Use when configuring precipitation, assigning gages to subbasins, updating TP40 to Atlas 14, modifying ET methods, or cloning met models for scenario comparison. Trigger keywords: met model, precipitation, gage assignment, Atlas 14, TP40, frequency storm, evapotranspiration, ET, meteorologic model, update precip.