Telemetry Plan — refactor-chain · docs (conditional)

Bundle: refactor-chain (self-diagnosing, self-healing fix-it pipeline). Phase: docs (conditional) · Prerequisite: the diff touched tracked/user-facing flows · Next: refactor-publish-checklist / refactor-ship. Adaptivity / conditional: conditional on a tracking-touch signal — activates only when analytics calls / event names / route or screen changes appear in the diff; otherwise reports "not applicable" and yields. Advisory-only.

Purpose

Analytics is fragile in a way tests don't catch: a refactor can rename an event, move a tracking call, or change a route/screen name that an event property depends on — the code still compiles, the tests still pass, and then a dashboard silently reads zero, a funnel breaks, or a running experiment loses its exposure event. This skill inspects the diff for anything that could break tracking, lists the specific events/properties at risk, and proposes an updated tracking plan for the changed flows so the team can keep instrumentation and code in lockstep.