From pm-skills
Specifies analytics dashboard requirements including metrics, visualizations, filters, and data sources. Use when requesting dashboards from data teams or defining KPI tracking.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pm-skills:measure-dashboard-requirementsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
A dashboard requirements document specifies what questions a dashboard should answer, what metrics it displays, and how data should be visualized. Clear requirements help data teams build dashboards that actually inform decisions rather than just displaying numbers.
measure-instrumentation-spec; instrument first, visualize secondmeasure-experiment-design and measure-experiment-resultsmeasure-okr-graderfoundation-okr-writer or define-problem-statementWhen asked to specify dashboard requirements, follow these steps:
Define the Purpose Start with the questions this dashboard should answer, not the charts it should show. What decisions will this dashboard inform? A dashboard without clear purpose becomes a vanity metrics display.
Identify the Audience Specify who will use this dashboard, how often, and in what context. An executive weekly review has different needs than a team's daily standup board.
Specify Key Metrics For each metric, document: name, business definition (in plain language), calculation formula, data source, and baseline/target values. Ambiguous metrics lead to misaligned dashboards.
Design Visualizations Recommend chart types based on what the data should communicate. Time trends need line charts; comparisons need bar charts; compositions need pie/treemaps. Include dimension breakdowns.
Define Filters and Segments Specify what drill-downs users need: date ranges, user segments, product areas, geographic regions. Anticipate the "slice and dice" questions users will ask.
Document Data Sources Identify where data comes from and any known data quality issues. Note latency requirements.does the dashboard need real-time data or is daily refresh sufficient?
Set Permissions and Access Determine who can view what. Some metrics may need restricted access. Consider both security requirements and organizational politics.
Use the template in references/TEMPLATE.md to structure the output. A complete spec fills every template section: Overview; Purpose and Questions; Audience; Key Metrics; Visualization Specifications; Filters and Segments; Data Sources; Access and Permissions; Alerts and Thresholds; Acceptance Criteria; Open Questions; and Appendix.
Before finalizing, verify:
See references/EXAMPLE.md for a completed example.
npx claudepluginhub product-on-purpose/pm-skills --plugin pm-skillsGenerates structured dashboard specifications from business questions, including KPIs, charts, filters, layouts, and data sources for BI developers using Looker, Metabase, or Grafana.
Use this skill when the user asks to "design a metrics dashboard", "what should be on my PM dashboard", "structure our analytics dashboard", "what metrics to track", "what should I put on a product dashboard", "build a metrics framework", or wants to design a coherent set of metrics and dashboard layout that drives good product decisions without creating information overload.
Builds or redesigns performance dashboards aligned to strategy using Balanced Scorecard and OKR frameworks. Guides metric selection, audience definition, and leading/lagging indicator separation.