analytics-requirements

Map stakeholder questions to business decisions and actionable metrics.

1|Updated Jun 20, 2026
One-click install
npx skills add https://github.com/shafibabar/SDLC-Artifact-Factory --skill analytics-requirements
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analytics-requirements
Source: https://github.com/shafibabar/SDLC-Artifact-Factory/tree/main/skills/analytics-requirements
Command: npx skills add https://github.com/shafibabar/SDLC-Artifact-Factory --skill analytics-requirements

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This skill prevents the common failure of building dashboards and reports that no one uses by forcing a decision-first approach to analytics, ensuring every metric serves a specific business action.

Core Features & Use Cases

  • Decision-First Elicitation: Guides stakeholders to identify the specific decision a metric informs before any build work begins.
  • Vanity-Metric Detection: Provides a rigorous six-point checklist to filter out metrics that look impressive but offer no actionable insight.
  • Traceability: Links every analytics requirement directly to OKRs or recurring operational decisions to ensure long-term relevance.

Quick Start

Use the analytics-requirements skill to scaffold a new requirements document for the data-estate-mapping product.

Frequently Asked Questions about analytics-requirements

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I define actionable metrics that drive business decisions?

Vanity metrics are identified using a rigorous six-point checklist designed to filter out impressive-looking data that offers no actionable insight. This validation process ensures retained metrics directly inform measurable business outcomes.

How do I elicit analytics requirements from stakeholders for dashboard specifications?

Yes, analytics requirements can be linked to OKRs by establishing traceability between every metric and recurring operational decisions. This ensures that dashboard and reporting specifications remain grounded in measurable business outcomes over time.

What is the best way to prevent building unused dashboards in data engineering?

The best way to prevent unused dashboards is to enforce a decision-first analytics design process that validates every metric against a specific business action. This approach resists vanity metrics and ensures reporting specifications are grounded in measurable outcomes.

Can I use a structured process to map stakeholder questions to specific metrics?

Yes, you can use a structured elicitation process to map stakeholder questions directly to specific metrics and business decisions. This prevents vanity-metric resistance by ensuring dashboard reporting specifications are traceable and actionable.