ddd-advisor

Recommends tactical DDD patterns for domain modeling problems.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/mikecubed/agent-orchestration --skill ddd-advisor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ddd-advisor
Source: https://github.com/mikecubed/agent-orchestration/tree/main/plugins/patterns/skills/ddd-advisor
Command: npx skills add https://github.com/mikecubed/agent-orchestration --skill ddd-advisor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Recommends tactical DDD patterns for domain modeling problems, helping teams decide whether a concept should be modeled as an Entity, a Value Object, a Service, or be modeled as part of an Aggregate, and guiding strategic boundaries when necessary.

Core Features & Use Cases

  • Provides practical guidance on selecting DDD building blocks (Entity, Value Object, Service, Aggregate) based on domain context.
  • Directs users to appropriate references and decision trees for deeper analysis, and clarifies when to escalate to strategy-oriented guidance.
  • Use Case: when designing a new domain module, consult this skill to obtain a recommended pattern and boundary guidance before implementation.

Quick Start

Ask a domain modeling question and I will apply DDD patterns to propose Entities, Value Objects, Aggregates, and Services.

Frequently Asked Questions about ddd-advisor

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

FAQPage Schema
How do I choose between an Entity and a Value Object during domain modeling?

Domain modeling pattern selection depends on identity and lifecycle tracking: Entities require identity for lifecycle tracking, while Value Objects represent attributes without identity. This skill applies DDD decision trees to recommend the appropriate building block based on your specific domain context.

When should I escalate tactical DDD patterns to strategic context mapping?

Strategic context mapping is necessary when tactical DDD patterns like Entities and Aggregates require boundary clarification across multiple domains. This skill directs users to strategy-oriented guidance when domain modeling questions exceed single-module scope.

How do I model an Aggregate boundary for a new domain module?

Aggregate boundary modeling requires grouping related Entities and Value Objects to ensure transactional consistency. This skill provides deterministic guidance via curated references and decision trees to recommend appropriate Aggregate boundaries before implementation.

Can I use domain-driven design decision trees for consistent pattern recommendations across teams?

Yes, domain-driven design decision trees enable consistent pattern recommendations by applying deterministic guidance via frontmatter metadata. This skill standardizes the selection of DDD building blocks like Aggregates and Services across multiple domain modeling conversations.

What are the limitations of using DDD tactical patterns without strategic context mapping?

Using DDD tactical patterns without strategic context mapping limits boundary guidance when concepts span multiple domains. This skill clarifies when tactical pattern selection is insufficient and recommends escalating to strategy-oriented guidance for broader architectural decisions.