V3 DDD Architecture

Modularize claude-flow v3 into bounded contexts with a microkernel plugin system.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/dzhechko/stt-rag-app --skill v3-ddd-architecture-dzhechko
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: V3 DDD Architecture
Source: https://github.com/dzhechko/stt-rag-app/tree/main/.claude/skills/v3-ddd-architecture
Command: npx skills add https://github.com/dzhechko/stt-rag-app --skill v3-ddd-architecture-dzhechko

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill modularizes claude-flow v3 by extracting a monolithic orchestrator into bounded contexts, enabling maintainable, testable, and scalable architecture.

Core Features & Use Cases

  • Bounded contexts per domain (task-management, session-management, health-monitoring, lifecycle-management, event-coordination)
  • Microkernel-based plugin system for extensibility
  • Clear domain interfaces and event-driven interactions to reduce coupling
  • Use Case: Reorganize existing orchestrator logic into dedicated domains with clean boundaries, enabling independent deployment and testing.

Quick Start

  • Task('Architecture analysis', 'Analyze current architecture and design DDD boundaries', 'core-architect')
  • 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')

Frequently Asked Questions about V3 DDD Architecture

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I break down a monolithic orchestrator into bounded contexts using DDD?▼

Domain-driven design decomposes a monolithic orchestrator by extracting domain logic into bounded contexts like task-management and session-management, establishing clear domain boundaries and event-driven interactions to reduce coupling.

What is a microkernel-based plugin system for modular architecture?▼

A microkernel-based plugin system provides extensible architecture by isolating core domain logic into bounded contexts, allowing plugins to integrate independently across task-management, session-management, and health-monitoring domains.

How do I map bounded contexts and relationships for domain decomposition?▼

Context mapping analyzes bounded contexts and their relationships by breaking down orchestrator god objects into dedicated domains, designing clean domain interfaces for independent deployment and testing.

Can I use TypeScript to enforce domain boundaries and event-driven interactions?▼

TypeScript supports enforcing domain boundaries and event-driven interactions by defining clear domain interfaces across bounded contexts, ensuring microkernel plugin systems interact with reduced coupling.

What is the best way to modularize a monolithic architecture for independent testing?▼

Modularizing a monolithic architecture involves extracting orchestrator logic into bounded contexts with clear interfaces and event-driven collaboration, enabling independent deployment and testing across isolated domains.

Why does domain decomposition reduce coupling in a microkernel plugin system?▼

Domain decomposition reduces coupling by enforcing bounded context boundaries and event-driven collaboration, allowing a microkernel plugin system to integrate extensions without tightly coupling core domains.