What problem does it solve? When a retail data warehouse has many tables at different readiness stages, it is hard to see which table is broken, which is blocked, and which one to fix next without opening every per-table status file. This Skill consolidates all committed per-table evidence into one worst-first portfolio view. ## Core Features & Use Cases - Per-table roll-up: One row per table showing stage, status, static WARN counts, live finding counts, open blockers, and next action, sorted worst-first. - Portfolio open-blockers list: Every open blocker across all tables with stage, concrete reason, measured evidence, and named owner, with unassigned blockers flagged. - Full traceability: Every number traces to a committed source file (readiness-status.yaml, data-issues.md, blocking-reasons.md) rather than a recomputation or invented score. - Use Case: Ask "which table do I fix next" and receive a ranked view where live validation errors (V-RC2/V-RC15/V-RC16) outrank static warnings, with each cell traceable to its source path. ## Quick Start Ask the assistant to show the data-quality control room for the repo and list which table to fix next.
