ddd-architect

To identify bounded contexts for a DDD architecture, the skill applies linguistic analysis to your domain description to discover core, supporting, and generic subdomains. It maps ubiquitous language and team boundaries into structured strategic artifacts.

Generating domain-driven design documentation involves translating complex domains into structured artifacts. You provide your domain description, and the system outputs executive summaries, context maps, glossaries, and ADRs directly into a docs/ddd directory.

Yes, you can design aggregates, invariants, domain events, and repository interfaces without manual coding. The tactical design process generates implementation guidelines and technical architecture documents automatically using predefined reference and asset templates.

Creating a context map to visualize bounded context relationships is part of strategic DDD mapping. It identifies subdomains and defines integration patterns between teams, outputting the mapped relationships as structured documentation under the DDD architecture folder.

You do not need extensive prior DDD knowledge to produce technical architecture and ADRs. By providing your domain description and requirements, the system automatically derives the strategic and tactical models, leveraging reference templates to generate implementable documentation.