V3 DDD Architecture
What This Skill Does
Designs and implements Domain-Driven Design (DDD) architecture for claude-flow v3, decomposing god objects into bounded contexts, implementing clean architecture patterns, and enabling modular, testable code structure.
Quick Start
DDD Implementation Strategy
Current Architecture Analysis
Domain Boundaries
1. Task Management Domain
2. Session Management Domain
3. Health Monitoring Domain
Microkernel Architecture Pattern
Core Kernel
Plugin Architecture
Domain Events & Integration
Event-Driven Communication
Clean Architecture Layers
Application Layer (Use Cases)
Module Configuration
Bounded Context Modules
Migration Strategy
Phase 1: Extract Domain Services
Phase 2: Implement Clean Interfaces
Phase 3: Plugin System
Testing Strategy
Domain Testing (London School TDD)
Success Metrics
- God Object Elimination: orchestrator.ts (1,440 lines) → 5 focused domains (<300 lines each)
- Bounded Context Isolation: 100% domain independence
- Plugin Architecture: Core + optional modules loading
- Clean Architecture: Dependency inversion maintained
- Event-Driven Communication: Loose coupling between domains
- Test Coverage: >90% domain logic coverage
Related V3 Skills
v3-core-implementation- Implementation of DDD domainsv3-memory-unification- AgentDB integration within bounded contextsv3-swarm-coordination- Swarm coordination as domain pluginv3-performance-optimization- Performance optimization across domains


