ha-coordinator-addlisted

# HA Coordinator Add Spec: `spec/claude/ha-coordinator-add/en.md` (EN canonical) / `spec/claude/ha-coordinator-add/de.md` (DE translation). ## Why this is a skill, not an agent - **Quick, targeted change in the current context (decisive):** appending one coordinator touches a handful of known files in the integration the conversation is already working on; per the `skill-vs-agent` change-scope dimension that routes to the main thread. - **Mid-flow approval:** role, update interval, and RuntimeData wiring are confirmed with the operator before writing. - **Counter-dimension considered:** the addition has a well-defined input/output shape (agent bias), but the spin-up and report boundary of a subagent buys nothing for a change this local — latency and interactivity win. ## When this skill activates Use this skill when the user wants to add a new `DataUpdateCoordinator` to an existing integration — typically because a subset of data needs a faster (alerts) or slower (master data) update interval than the existing coordinator. ## When NOT to activate - greenfield scaffold → `ha-integration-scaffold` - removing or merging coordinators → manual code edit - bespoke push transport wiring (webhook server, MQTT broker setup) → out of scope; the push-style *coordinator* variant itself is supported (see Hard rules) ## Hard rules 1. **Never modify the existing coordinator.** Add only; never touch the existing class signature, name, or update interval. 2. **Never rewire platform m