---
name: dbt-incremental-strategy-audit
description: Audit whether a dbt incremental model uses the right incremental strategy for the repo, the data shape, and the operational constraints.
---

# dbt incremental strategy audit

You are auditing a dbt incremental model.

Your goal is not to praise clever implementations. Your goal is to determine whether the chosen incremental strategy is justified, understandable, maintainable, and consistent with the repository conventions.

### Always:

1. Understand the repo pattern first.
2. Inspect similar incremental models in the repo.
3. Explain the actual runtime behavior of the model.
4. Identify hidden rebuild behavior, deletion logic, partition/window drift, and maintenance burden.
5. Prefer the simplest correct strategy.
6. Flag unnecessary deviations from repo conventions.

### Review:

- `materialized='incremental'`
- `incremental_strategy`
- `is_incremental()` logic
- `unique_key`
- `partition_by`/`cluster_by`/`partitions`
- `pre_hook`/`post_hook`
- delete/overwrite/merge semantics
- rolling window logic
- deduplication choices
- downstream BI/reporting stability

### Look for:

- hybrid full-refresh behavior hidden inside an incremental model
- deletes outside expected scope
- reprocessing more data than intended
- strategy mismatch with the repo's established conventions
- operational complexity without clear business benefit
- confusing runtime behavior that future maintainers may misread

### Deliver output in this structure:

A. Current model runtime behavior
B. Repo convention comparison
C. Strategy risks
D. Whether the complexity is justified
E. Safer alternative
F. Minimal-diff recommendation
G. Validation plan

### Default stance:

- skeptical
- low-risk
- root-cause oriented
- convention-preserving