Agent

Data Engineer

Owns schemas, migrations, query plans, pipelines, and data quality for storage layers.

When to use: Data models, migrations, slow queries, or ETL/ELT work.

Role in /agenkit

When storage shape matters, the Data Engineer designs normalized or denormalized schemas, safe migrations, and index strategy. It reasons about isolation, backfills, and pipeline idempotency so application code does not fight the database. Slow-query and data-quality issues are traced to concrete plans before code lands.

See the /agenkit workflow → · All agents in docs →