Data Analytics Router

Use this workflow when Data Analytics is explicitly invoked or the request requires structured records, quantitative evidence, metrics, or an evidence-backed product or business decision. Do not use it for ordinary prose drafting, file-format conversion, or qualitative description that does not require data interpretation.

Choose the focused workflow

• Metric changed, missed a target, or differs from expectation: read ../metric-diagnostics/SKILL.md.
• Product or business decision, prioritization, segmentation, launch, or experiment recommendation: read ../product-business-analysis/SKILL.md.
• Dataset, dashboard, source, join, freshness, grain, or metric trust question: read ../analyze-data-quality/SKILL.md.
• KPI framework, canonical definition, target, driver, or guardrail design: read ../design-kpis/SKILL.md.
• KPI status update, WBR, MBR, QBR, or operating readout: read ../kpi-reporting/SKILL.md.
• Dashboard or monitoring view: read ../build-dashboard/SKILL.md.
• Durable analytical report: read ../build-report/SKILL.md.
• Chart or quantitative figure: read ../visualize-data/SKILL.md.
• Reproducible SQL/Python notebook: read ../jupyter-notebooks/SKILL.md.
• TAM, SAM, SOM, segment, or opportunity sizing: read ../market-sizing/SKILL.md.
• Review an analysis before sharing: read ../validate-data/SKILL.md.
• Create, repair, or save reusable data context or a semantic layer: read ../create-data-context/SKILL.md.
• Missing business definitions, ownership, change context, or decision framing: read ../gather-business-context/SKILL.md before the primary workflow.

Load every selected workflow completely. Follow its related-skill rules when applicable. A task can combine workflows; use this usual order:

1. Gather missing business context.
2. Validate source quality and metric definitions.
3. Perform the focused analysis.
4. Validate conclusions.
5. Visualize or create the requested durable artifact.