ddd-strategic-design
Design DDD strategic artifacts including subdomains, bounded contexts, and ubiquitous language for complex business domains.
IT & Software Development[dddbounded-contextdddstrategic-designubiquitous-languageubiquitous-language]
DDD Strategic Design
Use this skill when
- Defining core, supporting, and generic subdomains.
- Splitting a monolith or service landscape by domain boundaries.
- Aligning teams and ownership with bounded contexts.
- Building a shared ubiquitous language with domain experts.
Do not use this skill when
- The domain model is stable and already well bounded.
- You need tactical code patterns only.
- The task is purely infrastructure or UI oriented.
Instructions
- Extract domain capabilities and classify subdomains.
- Define bounded contexts around consistency and ownership.
- Establish a ubiquitous language glossary and anti-terms.
- Capture context boundaries in ADRs before implementation.
If detailed templates are needed, open references/strategic-design-template.md.
Required artifacts
- Subdomain classification table
- Bounded context catalog
- Glossary with canonical terms
- Boundary decisions with rationale
Examples
Use @ddd-strategic-design to map our commerce domain into bounded contexts,
classify subdomains, and propose team ownership.Limitations
- This skill does not produce executable code.
- It cannot infer business truth without stakeholder input.
- It should be followed by tactical design before implementation.
Details
| Source | self |
|---|---|
| License | — |
| Risk label | safe ("critical" means the skill may run commands or touch files — read before use) |
| Files | SKILL.md, references/strategic-design-template.md |
| Added | 2026-02-27 |
Related skills
architect-review
Master software architect specializing in modern architecture
architecture
Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.
architecture-decision-records
Comprehensive patterns for creating, maintaining, and managing Architecture Decision Records (ADRs) that capture the context and rationale behind significant technical decisions.
architecture-patterns
Master proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design to build maintainable, testable, and scalable systems.
c4-architecture-c4-architecture
Generate comprehensive C4 architecture documentation for an existing repository/codebase using a bottom-up analysis approach.
c4-code
Expert C4 Code-level documentation specialist. Analyzes code directories to create comprehensive C4 code-level documentation including function signatures, arguments, dependencies, and code structure.