ddd-refactor

Analyze codebases to identify DDD anti-patterns and generate a phased refactoring plan.

Updated Jan 29, 2026
One-click install
npx skills add https://github.com/radkomih/claude-code-ext --skill ddd-refactor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ddd-refactor
Source: https://github.com/radkomih/claude-code-ext/tree/main/plugins/ddd-refactor/skills/ddd-refactor
Command: npx skills add https://github.com/radkomih/claude-code-ext --skill ddd-refactor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes codebases to identify DDD anti-patterns and provide an actionable refactor plan aligned with domain-driven design.

Core Features & Use Cases

  • Identify domain boundaries and ubiquitous language inconsistencies
  • Propose tactical patterns (Entity, Value Object, Aggregate, Repository, Domain Event)
  • Generate phased refactoring plan with concrete steps

Quick Start

Analyze a codebase to generate a DDD-aligned refactor plan with concrete steps.

Frequently Asked Questions about ddd-refactor

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

FAQPage Schema
How do I identify domain-driven design anti-patterns in my codebase?▼

This Skill analyzes your codebase to flag DDD anti-patterns like anemic models and ubiquitous language inconsistencies, then generates a targeted, actionable refactor plan.

What is the best way to refactor a monolith into bounded contexts?▼

The best way to refactor into bounded contexts is to map domain boundaries first, then apply tactical patterns like aggregates and domain events through a phased, incremental refactoring plan.

How do I apply tactical DDD patterns like aggregates and value objects correctly?▼

To apply tactical DDD patterns correctly, analyze domain models to ensure entities and value objects encapsulate aggregate roots, routing persistence through repositories for safe, incremental improvements.

Can I incrementally refactor domain models without breaking existing event-driven workflows?▼

Yes, you can incrementally refactor domain models without breaking workflows by following a phased plan that aligns domain events and event-driven considerations with safe, step-by-step code improvements.

Does this DDD refactor approach require prior knowledge of ubiquitous language?▼

No, this DDD refactor approach does not require pre-established ubiquitous language; it analyzes your existing codebase to identify ubiquitous language inconsistencies and proposes domain boundaries accordingly.

When should I not use domain-driven design refactoring?▼

You should avoid domain-driven design refactoring when your codebase lacks domain complexity to justify aggregate boundaries, or when mapping domain events and repositories provides no clear structural business value.