| name | dashboard-spec-writer |
| description | Define exactly what a product or ops dashboard should show, including metrics, dimensions, filters, and failure modes. Use when planning dashboards or analytics views. |
Dashboard Spec Writer
Overview
Define exactly what a product or ops dashboard should show, including metrics, dimensions, filters, and failure modes.
Core Workflow
- Gather the source material, existing conventions, templates, and destination format before drafting.
- Extract the information that matters most for the intended audience and discard low-signal noise.
- Structure the output so it matches repo, team, or domain expectations instead of starting from a blank generic outline.
- Draft the artifact, then surface any missing facts or decisions that still need human input.
Deliver
- A ready-to-edit draft in the expected structure and tone.
- The main sections, decisions, or states the artifact should include.
- Open questions or missing facts that would improve the final output.
Guardrails
- Do not invent facts, metrics, approvals, or guarantees that are not supported by the inputs.
- Prefer existing repo or team conventions over generic formatting.
- Keep the output useful and specific rather than padded.
- Do not invent metrics, policy decisions, customer commitments, or ownership that the inputs do not support.
