plenum-failure-archaeology

You can prevent regression during HVAC debugging by retrieving historical incident analyses and established fixes to check whether a proposed code change conflicts with previously accepted architecture decisions, tests, or safety guards.

Checking if a Plenum HVAC bug matches a resolved incident involves querying documented failure records containing symptoms, root causes, evidence, fixes, tests, and settlement status to retrieve matching historical analyses.

Incident history retrieval for HVAC control code review works by matching suspected bugs or proposed fixes against documented failure records, then extracting the root causes and evidence of past incidents to guide current architecture decisions.

Yes, you need documented failure records containing symptoms, root causes, evidence, fixes, tests, and status decisions to investigate smart thermostat bugs and avoid repeating previously resolved HVAC control failures.

You should check past incident settlements before changing HVAC architecture to identify when a proposed modification conflicts with established architecture decisions, tests, or safety guards implemented to resolve past failures.

A key limitation is that regression prevention guidance relies entirely on access to documented failure records; if an HVAC incident lacks documented symptoms, root causes, and fixes, the skill cannot provide relevant architectural guidance.