des-domain-modeling

What problem does it solve?

Prevents data engineering teams from designing schemas, pipelines, and analytics on top of vague terms, ambiguous grains, and unresolved source-of-truth decisions by forcing a conceptual domain model grounded in business meaning and Phase 05 source evidence.

Core Features & Use Cases

• Conceptual Domain Model for Phase 06: Defines a domain scope, business glossary, ontology-lite concept map, core entities, domain events, value objects, relationships, conceptual grains, identity rules, and domain rules without copying source schemas.
• Source alignment and evidence-backed mapping: Records where each domain concept is supported by sources, carries forward Phase 05 caveats, maps concepts to source-of-truth decisions, and documents terminology conflicts and synonyms.
• Validation-ready artifacts (Phase-Orchestrated Support): Produces required Phase 06 support plan, evidence pack, artifact revision notes, Done Gate result, and Phase 06→07 handoff so downstream architecture can proceed safely.

Quick Start

Use the des-domain-modeling skill to create _des-output/planning-artifacts/06-conceptual-domain-model.md using Phase 05 business context, source inventory, and the Phase 05→06 handoff.