tactical-ddd
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,
npx skills add tech-leads-club/agent-skills --skill tactical-ddd --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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](reference.md) directly | ### Phase 1 — Detect Load [detection.md](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 | Yes | **Aggregate** | | Operation spans multiple Aggregates/doesn't belong to any | — | **Domain Service** | Prefer Value Objects over Entities. Prefer small Aggregates over large ones. **If intent was validate/review**: stop here. Report findings using the
- Workflow
- Phase 1 — Detect
- Phase 2 — Assess
- Phase 3 — Refactor
- Quick Anemia Signals (scan first)
- Golden Rules
- Output Format
What does the tactical-ddd skill do?
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,
How do I install it?
Run `npx skills add tech-leads-club/agent-skills --skill tactical-ddd --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From tech-leads-club/agent-skills, a repository with 4,983 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.