ba-data-system-questioning

Guide stakeholders through structured questions to document data system requirements.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/Yukine5377/common --skill ba-data-system-questioning
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ba-data-system-questioning
Source: https://github.com/Yukine5377/common/tree/main/.cursor/skills/ba-data-system-questioning
Command: npx skills add https://github.com/Yukine5377/common --skill ba-data-system-questioning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps Business Analysts create a comprehensive set of questions to elicit deep requirements for data system projects (DWH, BI, Analytics, ETL), ensuring core data definitions and metrics are captured early.

Core Features & Use Cases

  • Tiered elicitation framework covering root cause, data sources, business logic, data lineage, and operational processes.
  • Artifact-oriented prompting that requests real-world documents like data dictionaries, Excel reports, and system queries to ground discussions.
  • Use Case: For a new Data Warehouse initiative, generate targeted questions to align stakeholders on how metrics are calculated and how data flows from source to dashboard.

Quick Start

Start by initiating a data-system requirements session and run this skill to generate a structured interview plan for a DWH/BI project.

Frequently Asked Questions about ba-data-system-questioning

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

FAQPage Schema
How do I elicit data warehouse requirements from stakeholders effectively?

Elicit data warehouse requirements by guiding stakeholders through a tiered framework of structured questions, covering root causes, data sources, lineage, and operational processes. This approach captures core definitions and metrics early for a ready-to-design foundation.

What questions should I ask when gathering BI dashboard requirements?

When gathering BI dashboard requirements, ask artifact-oriented questions that request real-world documents like data dictionaries and Excel reports. This grounds discussions and maps data sources to specific business metrics and calculation rules.

How do I document ETL business rules and data lineage for analytics projects?

Document ETL business rules and data lineage by enforcing a structured elicitation framework that requests existing system queries and artifacts. This maps the flow from source systems to final analytics outputs, ensuring all transformation logic is captured.

Can I use a structured questionnaire to align stakeholders on data system metrics?

Yes, you can align stakeholders on data system metrics by deploying a tiered questionnaire. It systematically guides stakeholders from root cause analysis to data usage, ensuring clear agreement on how metrics are calculated and how data flows.

What is the best way to start a data system requirements elicitation session?

Start a data system requirements session by generating a structured interview plan for DWH or BI projects. The plan enforces a tiered elicitation framework that immediately requests artifacts like data dictionaries to ground the discussion.

Does this requirements elicitation framework work for both DWH and ETL projects?

Yes, this requirements elicitation framework works for DWH, BI, Analytics, and ETL projects. It systematically discovers data sources, lineage, metrics, and business rules across these scopes to ensure a ready-to-design foundation.