ddd-refactor

One-line summary

Sequence a refactor toward DDD: identify the smell, name the target pattern, propose small behavior-preserving steps in order.

When to use this skill

• Existing code that the user already considers a problem.
• The user knows roughly which direction to refactor in.
• Migration of a legacy module toward a DDD model.

When NOT to use this skill

• The user just wants a review and isn't ready to refactor → route to ddd-review.
• The user is starting a new domain model from scratch → route to ddd-design.

Core content

The general pattern: name the smell, name the target shape, write small steps that preserve behavior, run tests between each step, commit after each.