model-requirements

Gather BigQuery data model requirements and validate dependencies for bqetl queries.

10|2|Updated Nov 6, 2025
One-click install
npx skills add https://github.com/mozilla/bigquery-etl-skills --skill model-requirements
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: model-requirements
Source: https://github.com/mozilla/bigquery-etl-skills/tree/main/model-requirements
Command: npx skills add https://github.com/mozilla/bigquery-etl-skills --skill model-requirements

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill guides requirements gathering for building and modifying BigQuery data models. It provides structured interviews for new models, analyzes existing queries to understand impact, validates dependencies, warns about downstream effects, and produces dual outputs: a stakeholder-facing requirements document and condensed working notes for SQL development.

Core Features & Use Cases

  • Structured requirements interviews for new models (grain, source data, business logic)
  • Impact and dependency analysis for existing queries (downstream consumers, changes required)
  • Dependency validation sequence (local schema/metadata → Glean Dictionary → DataHub)
  • Working notes generation to aid SQL development and handoffs

Quick Start

Ask me to plan a new model or modify an existing query. I will gather sources, validate dependencies, identify downstream impact, and produce a formal requirements document plus working notes.

Frequently Asked Questions about model-requirements

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

FAQPage Schema
How do I gather requirements for a BigQuery data model?

Structured requirements gathering for BigQuery models captures grain, source tables, business logic, and dependencies through stakeholder interviews. This Skill guides you through those interviews, validates dependencies against local schema, Glean Dictionary, and DataHub, then produces a formal requirements document and working notes for SQL development.

What happens when I modify an existing bqetl query—what downstream impact should I check?

Modifying existing bqetl queries can affect downstream consumers and dependent models. This Skill analyzes existing queries to identify downstream impact, flags affected tables and dependencies, and produces impact analysis so you can plan required changes and communicate with stakeholders.

How do I validate data model dependencies before building?

Dependency validation follows a sequence: check local schema and metadata first, then consult Glean Dictionary, and use DataHub as a last resort. This Skill automates that validation workflow to confirm all source tables and dependencies exist and are correctly specified before SQL development begins.

Can I use this for both new data models and editing existing queries?

Yes. This Skill applies to new model planning, edits to existing bqetl queries, stakeholder interviews, and architecture design. It handles structured requirements gathering for new models and impact analysis for modifications to existing tables, producing appropriate outputs for each scenario.

What's the difference between the requirements document and working notes this Skill produces?

This Skill produces two outputs: a stakeholder-facing requirements document that captures business logic and decisions, and condensed working notes for SQL developers that guide implementation details like grain, source tables, and dependencies.

When should I use this Skill versus handling data model planning manually?

Use this Skill when you need systematic dependency validation, downstream impact analysis, or when coordinating with multiple stakeholders. It reduces planning overhead by automating schema checks, flagging risks early, and producing dual outputs for both stakeholders and developers.