ha-integration-solutionlisted

Plans and orchestrates a complete Home Assistant Python custom-integration backend from a result-oriented device/cloud/API requirement, driven by a chosen quality-scale target tier (Bronze–Platinum), so the user never picks individual skills. Decomposes the requirement into a minimal dependency-ordered plan for the target tier, presents it for approval, then dispatches the owning integration ha-* skills — resolved from the live skill inventory at runtime, never from a frozen list — threading the domain and entity_ids between steps, optionally closing with CI validation and HACS-release readiness. Activate on "build an integration for device/API X", "build a Gold-tier integration for my Acme thermostat cloud API", or equivalent German requests. Do not activate for a single clear augment (the owning skill), a YAML automation solution (ha-automation-solution), a Lovelace frontend (ha-lovelace-solution), or deploying to a live HA instance (ha-integration-deployer agent). Supports resume on re-invocation.
nolte/claude-home-assistant · ★ 1 · AI & Automation · score 68

Install: claude install-skill nolte/claude-home-assistant

# HA Integration Solution Spec: `spec/claude/ha-integration-solution/en.md` (EN canonical) / `spec/claude/ha-integration-solution/de.md` (DE translation). This skill is the **front door** to the Python custom-integration backend cluster — the integration-side counterpart to `ha-automation-solution`. It does not generate any artifact itself — it decomposes the requirement, plans the dependency-ordered combination, and dispatches the owning individual skills, each of which owns its generation and spec conformance. ## Why this is a skill, not an agent - **Plan-before-generate gate** — the skill plan must be presented and explicitly approved before any generation; that human-visible gate is core to the contract and an agent's fire-and-forget shape would lose it. - **Mid-flow interactivity** — clarifying questions (protocol, auth type, entity domains, quality features), plan confirmation, and the "this is actually a YAML automation, not an integration" decision are per-run dialogues. - **Orchestrator that dispatches other skills** — the skill-orchestrates-skill default (see `skill-vs-agent`) keeps the entry point in skill form, like `ha-automation-solution` dispatching its authoring skills. - Counter-dimension considered: the per-building-block generation could run as parallel agents, but the plan approval and the `domain`/`entity_id` threading must stay visible in the user's context; skill wins. ## When this skill activates Use this skill when the user describes a **device/