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.
npx -y skills add spencermarx/open-code-review --skill "V3 DDD Architecture" --agent claude-codeInstalls into .claude/skills of the current project.
Select a file.
github/awesome-copilot
alirezarezvani/claude-skills
microsoft/win-dev-skills
github/awesome-copilot