dbt Development Release

Use this when data is already in the warehouse (e.g. via Fivetran, Stitch, or manual loads) and you need to build or extend the dbt transformation layer.

In-scope artifacts: requirements, conceptual_model, data_model, dbt, data_quality

Workflow

/wire:new                                         # release_type: dbt_development

/wire:requirements-generate <release-folder>      # Focus on transformation requirements
/wire:requirements-validate <release-folder>
/wire:requirements-review <release-folder>

/wire:conceptual_model-generate <release-folder>
/wire:conceptual_model-validate <release-folder>
/wire:conceptual_model-review <release-folder>

/wire:data_model-generate <release-folder>        # Read existing source schema + requirements
/wire:data_model-validate <release-folder>
/wire:data_model-review <release-folder>

/wire:dbt-generate <release-folder>
/wire:dbt-validate <release-folder>
/wire:utils-run-dbt <release-folder>
/wire:dbt-review <release-folder>

/wire:data_quality-generate <release-folder>
/wire:data_quality-validate <release-folder>
/wire:data_quality-review <release-folder>

/wire:archive <release-folder>

Tutorial available

A worked example of a dbt Development engagement — using a fictional client scenario with realistic command output, agent delegation, and reviewer decisions — is available in the Tutorial: dbt Development.

Tips for dbt-only releases:

Add any existing dbt project files (existing schema.yml, source definitions, SQL examples) to requirements/ before running data_model:generate — the AI will use them to understand the existing model structure and extend it correctly
Store SQL examples from the source database (schema introspection results, sample queries) so the AI understands actual column names and types

Tip: Run /wire:playbook-generate <release-folder> after requirements are approved.

Workflow​

Workflow