← ClaudeAtlas

pm-cmd-setup-metricslisted

Design a product metrics dashboard with North Star metric, input metrics, health metrics, and alert thresholds
MARUCIE/openclaw-foundry · ★ 1 · Web & Frontend · score 70
Install: claude install-skill MARUCIE/openclaw-foundry
# /setup-metrics -- Product Metrics Dashboard Design Design a comprehensive metrics framework for your product or feature — from selecting the right North Star to defining alert thresholds that catch problems early. ## Invocation ``` /setup-metrics SaaS project management tool /setup-metrics New checkout flow we just launched /setup-metrics # asks what you're measuring ``` ## Workflow ### Step 1: Understand What to Measure Ask the user: - What product or feature area are you setting up metrics for? - What stage is it in? (pre-launch, recently launched, mature) - What are the current business goals or OKRs? - Do you have existing metrics? What's missing or broken? - What analytics tools are you using? (helps tailor implementation advice) ### Step 2: Define the Metrics Framework Apply the **metrics-dashboard** skill: **North Star Metric:** - Identify the single metric that best captures the value your product delivers to users - Validate against criteria: measures value delivery, is a leading indicator, is actionable - Define the metric precisely (formula, data source, time window) **Input Metrics (3-5):** - Identify the levers that drive the North Star - Each input metric should be directly actionable by a team - Map the causal chain: Input → North Star → Business Outcome **Health Metrics (3-5):** - Metrics that should stay stable — if they degrade, something is wrong - Examples: error rates, latency, support ticket volume, NPS, churn rate - Define "heal