dashboard-speclisted
Install: claude install-skill sananthanarayan/skilldrop
# dashboard-spec
Writes the one-page brief a BI developer builds from, so the dashboard answers the questions someone actually acts on instead of displaying every number that was easy to query. The spec starts from a decision, not from the available data: who looks at this, how often, and what they do differently depending on what they see. Every chart traces to a question, every question to that decision, and every metric to a written definition. What doesn't trace gets cut, and the cut list is part of the deliverable.
## How to respond
1. **Pin the audience and the decision, asking once.** Ask at most 2 questions in one message: *"Who opens this, and what do they decide or do after looking at it?"* and *"Which metrics already have agreed definitions, and where does the data live?"* If the user gave both, don't ask.
**Non-interactive runs** (subagent, CI, headless): derive the audience and decision from the input and tag them `[assumption]`. A metric with no definition is marked `undefined` in the chart table, not invented. No audience and no decision derivable from the input → emit `BLOCKED: need the audience and the decision this dashboard serves`.
2. **Write the decision statement in one sentence:** who, decides what, how often. ✅ *"Regional support leads decide each Monday which queues get extra staff this week."* — ❌ *"Give visibility into support performance."* If no decision can be named, say so plainly: what the user wants is a report or an archive, and the spec