domain-modeling

Resolving ambiguous domain terminology requires defining precise context boundaries and maintaining a shared ubiquitous language. This Skill challenges unclear concepts and records the refined definitions in a CONTEXT.md glossary to align domain concepts with implementation decisions.

You need to record an architecture decision record when a design trade-off is difficult to reverse or requires historical context. This Skill identifies meaningful architectural trade-offs and creates focused ADRs to capture important software design decisions before they become hidden assumptions.

The best way to maintain a ubiquitous language is to distinguish related concepts and maintain a precise glossary. This Skill refines domain vocabulary by challenging unclear terminology and documenting the agreed-upon definitions within a CONTEXT.md file.

Documenting context boundaries and architecture trade-offs requires aligning domain concepts with implementation decisions. This Skill helps you define correct domain boundaries for systems like an ordering platform and records the resulting architectural decisions in ADR documentation formats.

This domain modeling approach requires maintaining specific documentation formats to function effectively. You must use and update CONTEXT.md for the domain glossary and ADR formats for architectural decisions to ensure domain concepts align with implementation choices.