amadeus-domain-modeling

Domain terminology alignment resolves ambiguous language by detecting conflicts, sharpening broad terms, and confirming shared glossary entries for bounded context mapping. Confirmed terms are then recorded into the appropriate artifact files.

Resolving domain boundary conflicts in DDD involves testing concept relationships with concrete scenarios to distinguish entities, value objects, contexts, and responsibilities. This ensures conceptual boundaries remain consistent and actionable across artifacts.

To distinguish shared glossary terms from intent-specific candidates, evaluate whether the concept requires broad team alignment or serves a narrower functional design. Confirmed shared terms are written to the glossary, while others remain intent notes.

You need to formalize domain contracts and model elements when terminology alignment and boundary analysis are complete. Confirmed model elements, boundaries, and contract decisions are written into the correct domain map and functional design files.

Domain modeling requires cross-checking existing workspace artifacts to validate terminology and boundaries. Without these source artifacts, the skill cannot confirm decisions or write refined glossary and context map outputs accurately.

Ambiguous domain language causes inconsistent functional design when broad terms and boundary responsibilities are not clarified. Sharpening these terms and testing concept relationships with scenarios prevents conflicts and maintains artifact consistency.