V3 DDD Architecture

Decomposing a monolith into bounded contexts requires identifying domain boundaries, separating responsibilities into focused modules, and defining clean architecture layers with proper dependency flow to reduce coupling. This process turns oversized orchestration logic into independent, testable business domains using entities, repositories, and domain events.

Planning clean architecture layers requires defining presentation, application, domain, and infrastructure layers with strict dependency-inversion boundaries. This Skill structures these layers to support testable, maintainable, event-driven modules by enforcing explicit entities, value objects, repositories, and use cases.

Yes, a microkernel plugin design supports extensible module loading and event-driven communication between domains. This Skill facilitates plugin and event design to allow independent bounded contexts to interact seamlessly through domain events without tight coupling.

You should decompose a central service orchestrator when it has become a god object and needs to be refactored into independent business domains. This Skill applies when a large, hard-to-maintain codebase requires turning oversized orchestration logic into a modular architecture that is easier to test and evolve.

For domain modeling before splitting a monolith, you need to define explicit entities, value objects, repositories, domain events, and use cases. This Skill requires these elements to establish dependency-inversion boundaries that support testable and maintainable event-driven modules.