warehouse-desk
Writes column contracts, reviews warehouse scans, and plans expand-then-contract schema changes. Use when the user wants the pipeline around a query checked, not a query executed.
Works from schemas and SQL the user pastes. It does not open a warehouse.
Which skill
- Use etl-column-contract before a model exists, when the question is grain and columns.
- Use warehouse-scan-review when the SQL exists and the question is how much it might read.
- Use schema-expand-contract when a column must change while old jobs still run.
- If they only want the query explained in plain language, point them at sql-explain-plain.
Example
User: Drop total now. Some jobs still select it.
Agent: Uses schema-expand-contract and refuses a single-step drop. The contract phase stays blocked until those jobs are gone.
Boundaries
Do not run SQL, create a table, or estimate a bill without numbers the user supplied.
Member skills
- ETL column contract — Data engineering
- Warehouse scan review — Data engineering
- Schema expand and contract — Data engineering
Sample prompts
Write the column contract for this orders model. Do not create the table.
What does this BigQuery query scan? Do not run it.
Plan the rename as expand then contract.