ddd-strategic-design

Domain-Driven Design (DDD) strategic design discovers natural boundaries by analyzing business concepts and relationships. This Skill guides systematic questioning to extract core domains, define bounded contexts, and clarify how different system areas interact—preventing costly rework from misaligned service splits.

A bounded context is a DDD concept that defines explicit boundaries around a cohesive domain model where a ubiquitous language applies consistently. Identifying bounded contexts prevents confusion from shared terminology having different meanings across teams and clarifies which teams own which parts of your system.

This Skill generates targeted question sets tailored to specific stakeholder roles—Product Managers, Domain Experts, and End Users—each addressing different aspects of your domain. Structured interviews uncover business rules, user workflows, and system constraints that define clear architectural boundaries.

Yes. This Skill is designed specifically for unclear system descriptions and early-stage exploration. It works through phase-based diagnosis to progressively clarify your domain, making it ideal when you lack complete requirements but need to establish foundational boundaries before implementation.

This Skill generates three standardized DDD outputs: Bounded Context Analysis (defining each domain area and its responsibilities), Context Maps (visualizing relationships between bounded contexts), and Ubiquitous Language glossaries (shared terminology within each context).

No. This Skill guides you through discovery regardless of prior DDD experience. It structures the analysis process so you extract domain knowledge systematically from stakeholders, documentation, and system descriptions—building expertise as you work.