| name | lakehouse |
| description | Table format and catalog guidance — delegates to architect-lakehouse agent.
Use when working with Iceberg, Delta Lake, catalogs, or migrating from legacy
table formats.
|
Lakehouse Command
Get guidance on Iceberg, Delta Lake, catalogs, and open table formats
Usage
/lakehouse <description-or-question>
Examples
/lakehouse "Set up Iceberg tables with partition evolution"
/lakehouse "Migrate from Hive to Iceberg on AWS"
/lakehouse "Compare Delta Lake vs Iceberg for our use case"
/lakehouse "Configure Unity Catalog for multi-cloud"
What This Command Does
- Invokes the architect-lakehouse agent
- Analyzes your table format or catalog requirements
- Loads KB patterns from
lakehouse and cloud-platforms domains
- Generates:
- Table DDL with partition strategies
- Catalog configuration (Unity, Polaris, Nessie)
- Migration scripts from legacy formats
- Compaction and maintenance procedures
Agent Delegation
| Agent | Role |
|---|
architect-lakehouse | Primary — Iceberg, Delta, catalog governance |
architect-data-platform-engineer | Escalation — when infra provisioning is needed |
de-spark-engineer | Escalation — when Spark read/write optimization is needed |
KB Domains Used
lakehouse — Iceberg v3, Delta Lake, catalog wars, DuckLake
cloud-platforms — platform-specific Iceberg/Delta patterns
spark — Spark table format integration
Output
The agent generates table definitions, catalog configs, and operational runbooks for your lakehouse setup.