What problem does it solve? Dashboard work in the Seshat BI repo spans several individually-governed capabilities (gap checks, planning, design, composition, QA) that users must wire together by hand, making it possible to reach visual implementation without a committed report purpose or approved metric contracts. This Skill sequences those shipped capabilities into one fail-closed journey that stops at the human blueprint review. ## Core Features & Use Cases - State-driven coordination: Reads committed repository state via a read-only coordinator helper to pick exactly one next allowed action or a named blocker, with no separate state file. - Hard governance gates: Enforces semantic_model_ready: pass before any data-bound design, requires approved metric contracts for every visual, and never self-grants dashboard_ready: pass. - Fail-closed blockers: Every stop names what is missing, the evidence checked, the responsible owner, and the unblocking action, with no numeric scores. - Use Case: Given an approved Report Intent for a retail subject area, drive gap detection, duplicate-page checks, contract-bound design, report composition, and dashboard QA, then stop with a reviewable blueprint package for the named report owner. ## Quick Start Ask the agent to coordinate the dashboard work end to end for a subject area that already has an approved report intent and a passing semantic model readiness gate.
