ddd

Identify DDD violations and produce structured improvement steps for bounded contexts.

8|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/j0ruge/skills_commands_manager --skill ddd-j0ruge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ddd
Source: https://github.com/j0ruge/skills_commands_manager/tree/main/plugins/ddd/skills/ddd
Command: npx skills add https://github.com/j0ruge/skills_commands_manager --skill ddd-j0ruge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The DDD toolkit analyzes codebases to identify domain-driven design issues, surface boundary signals, and surface actionable improvements for effective bounded contexts, aggregates, and strategic design.

Core Features & Use Cases

  • Automated assessment against DDD patterns, including entities, value objects, aggregates, domain events, and read models.
  • Guidance for strategic design, covering event storming, bounded contexts, and context mapping to align teams and architecture.
  • Support for conversion from legacy systems to DDD, including ADRs, design-level explorations, and actionable refactoring steps.
  • Knowledge transfer via canonical references and practical examples to accelerate DDD adoption.

Quick Start

Provide the path to your repository to start the DDD assessment and retrieve initial recommendations.

Frequently Asked Questions about ddd

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

FAQPage Schema
How do I identify domain-driven design violations in my codebase?

You can identify DDD violations by providing your repository path for automated assessment against entities, value objects, aggregates, and domain events. The analysis produces structured reports containing findings, scope, and incremental refactoring steps for domain-model improvement.

What is bounded context mapping and when do I need it for strategic design?

Bounded context mapping defines explicit relationships and boundaries between domain models to align teams and software architecture. You need it when managing complex domain integrations or converting legacy systems, utilizing event storming to guide strategic design decisions.

How do I refactor a legacy system to use domain-driven design patterns?

Refactoring legacy systems to DDD requires analyzing existing code for boundary signals and applying canonical patterns to establish bounded contexts. This generates actionable refactoring steps and architecture decision records to guide incremental domain-model conversion.

Can I use event storming to align my architecture with bounded contexts?

Yes, event storming maps domain events and boundaries to align team architecture with bounded contexts. This strategic design technique surfaces actionable improvements for structuring aggregates and defining context mappings across complex domain models.

Does domain-driven design analysis require specific architectural dependencies?

No, domain-driven design analysis requires no external architectural dependencies to evaluate your codebase. It operates standalone, assessing your repository against canonical DDD patterns to identify structural violations and generate strategic bounded context recommendations without external tool constraints.