What problem does it solve?
des-transformation-design helps you define transformation logic clearly and safely so downstream layers can be implemented without guessing, while ensuring contract alignment, grain correctness, dependency order, incremental/backfill behavior, and testable validation expectations across Bronze → Silver → Gold.
Core Features & Use Cases
- Transformation specification (design, not code): Produce a Transformation Specification that captures scope, non-scope, principles, inventory, and layer-to-layer mapping.
- Dependency, mapping, and grain definition: Define the dependency graph, input/output dataset mapping, and the exact output grain to prevent incorrect joins, premature aggregation, and ambiguous entity meaning.
- Rules for business logic and data behavior: Specify business rules, cleaning/conformance rules, join/relationship rules, deduplication/survivorship rules, SCD/history handling, aggregation/metric calculation rules, incremental strategy, backfill/replay, late/corrected data behavior, error/quarantine behavior, and validation expectations.
- Contract-aligned traceability: Ensure contracted outputs map to transformation paths and record lineage and metadata expectations for evidence-driven handoff.
Quick Start
Use the des-transformation-design skill when your Phase 12 data contract and Bronze/Silver/Gold layer designs exist and you need a Phase 13 Transformation Specification before writing any SQL or pipeline code.
