Use ONLY for genuine architectural crossroads — decisions with broad, hard-to-reverse impact: new storage layer, migrating Silver storage format, adding a new medallion tier, major schema changes that ripple across all layers, evaluating DuckLake vs DuckDB trade-offs, reviewing a complex multi-file PR for correctness…
Default agent for all implementation work — Python modules, dbt SQL and macros, Dagster assets/jobs/schedules/sensors, dlt pipelines, configuration changes, and pytest tests. Use this for any task that results in a code commit. Only escalate to the architect agent when facing a genuine architectural crossroads (new…
Use when something is broken or behaving unexpectedly — Dagster run failures, silent dlt extraction errors, DuckDB state that doesn't match expectations, Metabase connection issues, CI failures, test failures with unclear causes. Read-only mindset: diagnose first, propose fixes second. Do not use for greenfield…
Use for writing or updating documentation (markdown in documentation/, CLAUDE.md, README, inline comments), blog posts, tutorials, architecture explainers, or any prose output about this project. Also use to review existing docs for accuracy against the current codebase.
Analyse the following task, identify ALL agents from the project team in .claude/agents/ whose expertise is relevant, spawn them, and synthesise their outputs into a single cohesive answer for the user.
Instructions for edwinweber/dbt_duckdb_demo_public, covering claude.md — project context for ai assistants, project overview, tech stack, architecture and directory structure.