ha-esphome-solutionlisted

Plans and orchestrates a complete ESPHome device or fleet result from a requirement, so the user never has to pick which ESPHome skill produces what. Decomposes it into the minimal dependency-ordered set of artifacts across the ha-esphome-* family — repository layout and packages, the device file, sensors and buses, Home-Assistant-driven bindings, display content, the voice satellite, CI validation — presents that plan for approval, then dispatches the owning skills resolved from the live inventory at runtime, threading device identities, package parameters, and entity ids between steps. Generation only: it never compiles, flashes, or rolls out, and never runs the review itself — the read-only reviewer agents stay a separately triggered pass, so an artifact is never judged by its own author. Activate on "build me an ESPHome device for…", "set up my ESPHome fleet", or equivalent German requests. Do not activate for a single clear artifact (the owning skill). Supports resume.
nolte/claude-home-assistant · ★ 1 · AI & Automation · score 68

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

# HA ESPHome Solution Spec: `spec/claude/ha-esphome-solution/en.md` (EN canonical) / `spec/claude/ha-esphome-solution/de.md` (DE translation). This spec governs the front-door dispatch/plan contract, structurally consistent with its `ha-{integration,lovelace,automation,pixoo}-solution` siblings; the grounding specs below govern the ESPHome artifacts themselves. Grounding specs: `spec/ha/esphome-config-patterns/en.md`, `spec/ha/esphome-project-structure/en.md`, `spec/ha/esphome-ha-driven-content/en.md`, and — where the device is one — `spec/ha/esp32-s3-box/en.md`, `spec/ha/esp32-s3-box-display/en.md`, `spec/ha/assist-pipeline/en.md`. This skill is the **front door** to the ESPHome skill family. It generates nothing itself: it decomposes the requirement, plans the combination, and dispatches the owning skills, each of which owns its generation and spec conformance. ## Why this is a skill, not an agent - **Plan-before-generate gate** — the artifact 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** — the clarifying questions (which board, which values come from Home Assistant, is there a screen, is it a voice satellite) and the plan confirmation are per-run dialogues. - **Orchestrator that dispatches other skills** — the skill-orchestrates-skill default keeps the entry point in skill form, exactly as the sibling `*-solution` ski