analytics-and-warehouse-design

Design governance-backed analytics architectures with layered data models and metric ownership.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/Tiepbm/software-engineering-agent --skill analytics-and-warehouse-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analytics-and-warehouse-design
Source: https://github.com/Tiepbm/software-engineering-agent/tree/main/skills/analytics-and-warehouse-design
Command: npx skills add https://github.com/Tiepbm/software-engineering-agent --skill analytics-and-warehouse-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designs governance-backed analytics architectures to ensure consistent data grain, lineage, metric ownership, and reproducible reports across warehouses, lakehouses, and semantic layers.

Core Features & Use Cases

  • Layered analytics architecture guiding Raw, Staging, Curated Core, Mart, Semantic, and BI layers to ensure data quality and governance.
  • Explicit metric definitions, slowly changing dimensions handling, and certified datasets to enable cross-domain reporting.
  • Use Case: Build a star-schema data mart for a marketing analytics dashboard with clearly owned metrics and reconciliation checks.

Quick Start

Define the grain, dimensions, and metrics for a new analytics warehouse and specify the data contracts between layers.

Frequently Asked Questions about analytics-and-warehouse-design

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

FAQPage Schema
How do I design a data warehouse architecture with clear lineage and metric ownership?

Designing a governed data warehouse requires a layered architecture guiding Raw, Staging, Curated Core, Mart, Semantic, and BI layers to ensure data quality, explicit metric definitions, and clear lineage across domains.

What is the best way to build a star-schema data mart for marketing analytics with certified datasets?

Building a marketing analytics data mart involves defining the grain, dimensions, and metrics, then specifying data contracts between layers to establish certified datasets with reconciliation checks and explicit ownership.

How does a semantic layer handle slowly changing dimensions and reproducible transformations?

A semantic layer handles slowly changing dimensions by enforcing explicit metric definitions and layered architecture, ensuring transformations remain reproducible and reports stay consistent across cross-domain queries.

Can I apply lakehouse architecture to finance and product analytics with cost controls and data contracts?

Yes, you can apply lakehouse architecture to finance and product analytics by defining data contracts between layers, specifying grain and metrics, and implementing explicit ownership to maintain cost controls and certified datasets.

When do I need data contracts and reconciliation checks in my analytics architecture?

You need data contracts and reconciliation checks when transforming operational data into governed analytical assets, ensuring reproducible reports, consistent data grain, and certified datasets across domains like marketing and finance.