ha-config-flow-augmentlisted

# HA Config Flow Augment Spec: `spec/claude/ha-config-flow-augment/en.md` (EN canonical) / `spec/claude/ha-config-flow-augment/de.md` (DE translation). ## Why this is a skill, not an agent - **Mid-flow approval is the contract (decisive):** augmenting a live config flow edits an existing integration; the pattern choice and the plan are confirmed with the operator before any write, and follow-up corrections continue in the same thread. - **Context access:** which integration, which flow pattern, and which existing conventions apply comes from the open conversation and repo state, not from a self-contained input. - **Counter-dimension considered:** applying one known pattern is a well-defined unit (agent bias), but losing the approval gate in a fire-and-forget agent would let structural flow changes land unreviewed — interactivity outweighs. ## When this skill activates Use this skill when the user wants to: - retrofit a tenant / account selection step after the auth step - retrofit zeroconf discovery into a config flow that did not initially carry it - retrofit a reauth flow - retrofit a reconfigure flow - add OAuth as a parallel auth path next to the existing API-key path ## When NOT to activate - greenfield integration scaffolding → `ha-integration-scaffold` - pure schema edits (rename a field, change a default) → manual code edit - destructive refactors (remove a step, rewrite a step) → manual code edit with explicit user approval - schema migration of `entry.data`