tactical-ddd

name

tactical-ddd

description

Detects anemic domain models, validates and refactors them into rich domain models, and enforces tactical DDD patterns (Entities, Value Objects, Aggregates, Domain Services, Domain Events). Use when the user asks to validate, review, or check domain models or DDD code; detect anemia; refactor domain objects; improve encapsulation; or mentions terms like "anemic model", "rich domain", "aggregate", "value object", "domain event", "ubiquitous language", "is this good DDD", "does this follow DDD", or "check my domain". Do NOT use for module or service boundary design, architectural decomposition, strategic DDD context mapping, or code outside the domain layer (DTOs, controllers, infrastructure adapters).

Tactical DDD — Rich Domain Modeling

Workflow

Determine the user's intent first:

Intent	Phases to run
"validate / review / check / is this correct?"	Phase 1 + 2 only → report findings, ask before refactoring
"fix / refactor / improve / clean up"	Phase 1 + 2 + 3
"how should I design / model this?"	Load reference.md directly

Phase 1 — Detect

Load detection.md and scan the target code for anemia signals. Produce a severity score and list of affected classes.

Phase 2 — Assess

For each affected class, determine the correct building block:

Has unique identity tracked over time?	Has invariants tying multiple objects?	→ Building Block
Yes	—	Entity
No	—	Value Object
Yes (root) + children with shared invariants