Turn a vague request into a design spec

Someone asked for "a dashboard" and then walked away.

Turn this vague request into something a designer and an engineer could both build from.

1. Restate the request as the underlying user problem. If several readings are possible, list them and say which you think is meant.
2. Ask me the questions that genuinely block progress, at most five, ordered by how much each changes the design.
3. Assume plausible answers for everything else, and label every assumption.
4. Write the spec: all states, including loading, empty, error, and permission denied; the data shown and where it comes from; every interaction and what it changes; the edge cases needing a decision.
5. List what is explicitly out of scope.

Do not design it yet. The output is a definition precise enough that two people working separately would build the same thing.

Request:

Briefs and decisions. The work around the design: turning a request into a brief, choosing between options, writing down why.