build-dashboard-healthlisted

# Build: /health-check You are about to generate a `/health-check` skill customised to this company's estate and lifecycle rules. Complete all three phases first. ## Phase 1 — Inspect 1. **Check estate access.** MCP server, BI tool API, admin exports — same drill as `/build-dashboard-triage`, and if that builder already ran, reuse its answer. The health loop needs *repeatable* access; if the only path is a manual export, the generated skill will define the export-refresh step as part of the cadence rather than pretending to be continuous. 2. **Find the lifecycle metadata that exists today.** Certification badges, folder conventions implying status, tags, a governance register. Most estates have fragments; the skill builds on what exists rather than inventing a parallel system. 3. **Map the drift signals available.** For each, check whether the data is reachable: - **Upstream drift:** dbt models changed (`git log`) since the dashboard was last verified - **Ownership drift:** owner field vs current staff (leavers are findable in the BI tool's user list) - **Usage drift:** view counts decaying toward zero - **Breakage:** tiles erroring, queries failing, columns missing 4. **Check for a triage baseline.** If `/dashboard-triage` verdicts exist, the health loop starts from them; if not, note that the first health run doubles as a rough audit. ## Phase 2 — Interview 1. **"What are your lifecycle stages — or shall we use the four that survived production?"** Draft /