Clarify domain boundaries and model core concepts with bounded contexts and context maps.
npx skills add https://github.com/resultakak/argos --skill ddd-modeling-resultakak
Please help me install this Agent Skill. Skill: ddd-modeling Source: https://github.com/resultakak/argos/tree/main/skills/ddd-modeling Command: npx skills add https://github.com/resultakak/argos --skill ddd-modeling-resultakak
Domain modeling often suffers from ambiguous terminology and scattered definitions across teams. This skill provides a structured approach to define bounded contexts, ubiquitous language, context maps, aggregates, entities, value objects, domain events, and event-storming outputs to align teams and guide architecture.
Begin by identifying a domain boundary and run a quick event-storming session to draft a bounded-context canvas and a domain glossary.
High-intent search queries and answers about installing and using this skill.
Defining bounded contexts requires establishing a canonical ubiquitous language to clarify domain boundaries and model core concepts. This structured approach prevents semantic drift by aligning teams and guiding architecture decisions through documented context maps.
Modeling domain events and aggregates involves structuring domain objects to establish clear boundaries and event-driven workflows. This technique surfaces hot spots during event-storming sessions, reducing cross-team miscommunication and guiding early domain discovery.
Creating a context map visualizes team-context relationships and interactions to align multiple teams on architecture decisions. It documents the connections between bounded contexts, reducing cross-team miscommunication and clarifying domain boundaries.
Event-storming is used to draft a bounded-context canvas and a domain glossary during early domain discovery. This workshop technique surfaces hot spots and architectural decisions, establishing a ubiquitous language and defining aggregates.
Documenting architecture decisions via ADRs is needed when modeling core domain concepts across multiple teams to prevent semantic drift. This occurs during bounded-context design and context-map creation to establish clear domain boundaries.
Domain modeling suffers from ambiguous terminology and scattered definitions due to a lack of a canonical ubiquitous language across teams. Establishing bounded contexts and documenting decisions via context maps resolves this miscommunication.
AIGNE-ioTranslate Doc-Smith documentation into multiple languages with glossary consistency.
arbazkhan971Model complex business domains into bounded contexts, aggregates, and event catalogs.
jwilgerGuide structured event modeling workshops for event-sourced systems.
JoeyJoziahDecompose monolithic application logic into bounded contexts and modular domains.
