V3 DDD Architecture

This breaks down monolithic orchestrator code into proper domain boundaries using DDD patterns. You'd use this when refactoring claude-flow v3 projects that have grown into god objects, especially if you're dealing with something like a 1,440-line orchestrator file that mixes task management, session handling, and health monitoring. It implements a microkernel pattern where each domain (task management, session management, health monitoring) gets its own entities, value objects, and repositories, all wired together through a domain event bus. The plugin architecture is clean, you can bolt on things like swarm coordination without touching core domains. Good fit if you're serious about making your Claude automation code maintainable at scale rather than just hacking features onto a growing mess.

GitHub stars: 240
last updated: Jun 11, 2026

View on GitHub

Install

$ npx -y skills add spencermarx/open-code-review --skill 'V3 DDD Architecture' --agent claude-code

Installs into .claude/skills of the current project.

Files

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

# Initialize DDD architecture analysis
Task("Architecture analysis", "Analyze current architecture and design DDD boundaries", "core-architect")

# Domain modeling (parallel)
Task("Domain decomposition", "Break down orchestrator god object into domains", "core-architect")
Task("Context mapping", "Map bounded contexts and relationships", "core-architect")
Task("Interface design", "Design clean domain interfaces", "core-architect")