What problem does it solve? Teams splitting monoliths or designing new systems often draw service boundaries along technical layers, producing distributed monoliths, shared databases, and conflicting terminology. This Skill guides the strategic side of Domain-Driven Design so boundaries align with business capabilities and team ownership. ## Core Features & Use Cases - Subdomain Classification: Categorizes capabilities as Core, Supporting, or Generic to drive build-vs-buy decisions. - Bounded Context & Context Mapping: Defines context boundaries by consistency scope, team ownership, and language, then maps relationships (Shared Kernel, Customer-Supplier, Anti-Corruption Layer, Open Host Service). - Ubiquitous Language Glossary: Produces a term glossary with banned synonyms enforced across code, database columns, and API fields. - Use Case: When decomposing a monolith into services, use this Skill to extract domain capabilities, classify subdomains, define bounded contexts, and record each boundary decision as an ADR before writing any code. ## Quick Start Ask the agent to apply DDD strategic design to define bounded contexts and a ubiquitous language glossary for your domain, for example an e-commerce order and logistics system.