Tour an unfamiliar dbt project at "The Builder Depot" using dbt Wizard. Seven steps: inventory the models, sample real data, read tests and contracts, then create and preview a new mart model (orders_by_week). Nothing is materialized.
Onboarding scenario walkthrough.
First week at The Builder Depot. You have access to the dbt repo and a mandate to "get familiar with the project and ship something small by Friday."
The seven steps cover orientation (folder layout, model inventory by layer and domain, grain and lineage of the headline mart, sampled rows, test coverage) and then ship a new mart model that compiles and previews.
orders_by_week as a previewed, compiled, non-materialized model.
Copy each prompt as written, or rephrase. Run in order.
dbt Wizard reads the project as a whole and returns the subject areas and layering.
Summarize what this dbt project does. What are the main subject areas and how is the project organized?
Then group the models by layer and domain.
List the staging, intermediate, and mart models. Group them by domain.
Bucket the model list by layer and by domain to map the project's two axes.
Show me the lineage, grain, and key columns for the orders mart model.
The orders mart sits at the busiest join in the project. Name the grain explicitly before continuing.
Show me a 10-row sample of the orders mart and the distinct values in the order_status column.
The distinct values for order_status are the reference list for filters used in later steps. Capture them now.
What tests and contracts are defined on the orders model? Are any currently failing?
The test list documents the model's invariants. The list of currently failing tests points to active problems in the project.
Create a new mart model called orders_by_week that aggregates orders to the week grain with order count, gross revenue, and distinct customers.
dbt Wizard writes orders_by_week.sql into models/marts/, built on the orders mart (not on staging), with convention-aware naming and date truncation.
Compile and preview orders_by_week. Don't materialize it.
The model compiles, a sample of weekly rows renders, nothing lands in the warehouse. The deliverable is the reviewable orders_by_week.sql file.
order_count, gross_revenue, and distinct_customers, and a date column where every value is a week-start.
models/marts/orders_by_week.sql - a mart model at the week grain with order_count, gross_revenue, and distinct_customers. Compiled and previewed. Not materialized.
Skill definition, prompts, and instructor notes for onboarding.
Every prompt in this scenario, formatted for print.
Inventory misallocation investigation.