What problem does it solve? Hardware test artifacts (simulator fixtures, firmware configs, integration tests) are often generated independently, causing inconsistent values and behavior. This Skill produces a single Canonical Test Specification from a chip's ESPHome component source and docs, acting as the one source of truth for all downstream code generation. ## Core Features & Use Cases - Canonical Spec Generation: Produces a minimal, deterministic, implementation-independent YAML-style specification describing observable device behavior (observables, units, defaults, presentation templates). - Hallucination Prevention: Requires every value to trace to an authoritative source (datasheet, ESPHome component source, reference driver) and mandates status: unknown instead of guessing. - Single Source of Truth for Defaults: Defines one default value per observable consumed by both simulator chips and test harnesses, preventing silent simulation-time mismatches. - Use Case: Given the ESPHome component source and docs for a TMP102 sensor, generate test_spec_tmp102.md so downstream skills can build a Wokwi custom chip and a serial-output test harness that agree on the emitted and asserted temperature value. ## Quick Start Generate a canonical test specification for the TMP102 device using the ESPHome component files in the outputs directory.