added skills etc

.agents/skills/evolv-orchestrator/SKILL.md

@@ -0,0 +1,52 @@
+---
+name: evolv-orchestrator
+description: Orchestrate multi-agent execution for the EVOLV repository. Use when work spans multiple disciplines (Node-RED frontend/editor UI, rotating equipment logic, instrumentation assets, process control, InfluxDB/data architecture, OT/IT security, and quality/technical debt) and requires decomposition, sequencing, handoffs, and integration decisions.
+---
+
+# EVOLV Orchestrator
+
+## Mission
+Coordinate specialized EVOLV agents, split work into clear tasks, and ensure integrations are coherent across JavaScript/CommonJS Node-RED nodes, process assets, and observability/data concerns.
+
+## Execution Flow
+1. Frame the objective and constraints in one paragraph.
+2. Identify impacted areas in the repo before assigning work:
+- `nodes/<nodeName>/<nodeName>.html` (editor UI)
+- `nodes/<nodeName>/<nodeName>.js` (runtime entry)
+- `nodes/<nodeName>/src/nodeClass.js` (Node-RED wrapper)
+- `nodes/<nodeName>/src/specificClass.js` (domain logic)
+- `nodes/generalFunctions/` (shared helpers/config)
+3. Route tasks to specialist skills with explicit deliverables and acceptance criteria.
+4. Require each specialist to return:
+- assumptions
+- changed files
+- tests added/updated
+- unresolved risks
+5. Integrate outputs and check cross-skill consistency:
+- config fields aligned between `.html` and runtime parsing
+- admin endpoints stable (`/<nodeName>/menu.js`, `/<nodeName>/configData.js`)
+- topic contracts (`msg.topic`) unchanged unless migration is defined
+6. Ask targeted user interview questions only when decisions are ambiguous and unblock execution.
+7. Produce a final integrated plan or implementation with a risk log.
+
+## Delegation Map
+- Use `evolv-frontend-node-red` for Node-RED editor/runtime UX and HTML config input design.
+- Use `evolv-mechanical-rotating-equipment` for rotating machine behavior, limits, and performance logic.
+- Use `evolv-instrumentation-assets` for measurement tags, sensor semantics, and asset metadata.
+- Use `evolv-process-systems-control` for system-level interactions, modes, and control architecture.
+- Use `evolv-database-influx-architecture` for InfluxDB schema, retention, query shape, and Grafana coupling.
+- Use `evolv-ot-it-security` for OT/IT hardening and secure-by-default checks.
+- Use `evolv-quality-technical-debt` for regression risk, tests, maintainability, and technical debt.
+
+## Interview Protocol
+Ask at most 3 focused questions at a time. Prioritize:
+1. Operational objective and KPI (what "better" means).
+2. Safety/availability constraints (what must never break).
+3. Backward compatibility expectations for flows and topics.
+
+## Output Contract
+Return:
+- task breakdown by specialist
+- execution order and dependencies
+- measurable acceptance criteria
+- integration risks and mitigation