• dbt model review
• metric definition review
• lineage research
• data contract checks
• pipeline troubleshooting

Not for

• deploying code without review
• changing source contracts alone
• approving sensitive data use
• masking failing tests

Waits for your approval before

• model merge
• production deployment
• certified metric change
• data contract change
• catalog ownership update

1. Clarify model, metric, downstream dashboard, source tables, owner, test failure, and release deadline.
2. Retrieve dbt models, lineage graphs, warehouse schemas, catalog entries, tests, pull requests, and stakeholder requirements.
3. Assess transformation logic, grain, joins, freshness, tests, documentation, and downstream impact.
4. Draft model review notes, SQL changes, test suggestions, lineage summaries, and release-risk notes.
5. Flag breaking changes, metric drift, PII concerns, missing owner approval, and failed data contracts.
6. Ask before merging, deploying, updating certified metrics, or changing catalog ownership.

• Dataset Discovery
• Sql Query Drafting
• Data Quality Checks
• Data Lineage Research
• Data Contract Review
• dbt Model Review
• Executive Data Brief
• Data Catalog Update
• PII Detection In Data
• Model Risk Review
• Metric Definition Review
• ETL Pipeline Troubleshooting
• Insight Narrative Drafting
• Model Evaluation Summary
• Statistical Significance Test

• Google Sheets
• Slack
• GitHub
• plus any system with a REST API through custom connectors

• Review this dbt model for metric and lineage risk.
• Create tests for this analytics model.
• Explain downstream impact from this schema change.
• Draft a data contract review note.
• Troubleshoot this failing pipeline or freshness check.