ddd-strategist

Identify bounded contexts and map their relationships for strategic DDD decisions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Bounded Context discovery and Context Map creation tool. Invoke when the user asks "should these be separate bounded contexts", "help me draw a context map", "how should these services integrate", "we have a legacy system to integrate", "should we use an Anticorruption Layer or Conformist", "what's my Core Domain", "how should these teams relate", or describes a system/team structure and wants strategic DDD guidance. This skill operates at the system/team level, not code level. Do NOT invoke for code-level domain modeling (use ddd-advisor). Do NOT invoke for code evaluation (use ddd-evaluator).

Core Features & Use Cases

  • Bounded Context discovery and Context Map creation to clarify system boundaries
  • Core Domain identification and essential integration pattern guidance
  • Context-driven collaboration guidance for teams and services
  • Guidance on strategic relationships between contexts (customer/supplier, shared kernel, ACL considerations)

Quick Start

Describe your system, teams, and integration needs to generate a strategic context map.

Frequently Asked Questions about ddd-strategist

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

FAQPage Schema
How do I identify bounded contexts for a new system architecture?

To identify bounded contexts, you describe your system and team structure to validate boundaries and generate a strategic context map. This clarifies domain boundaries to guide system-level planning and integration decisions across new architectures.

When do I need an Anticorruption Layer versus a Conformist relationship?

You need an Anticorruption Layer to isolate a legacy system, whereas a Conformist relationship aligns a dependent context with an upstream model. Selecting the right integration pattern depends on validating boundaries and team alignment within your context map.

What is the best way to draw a context map for microservices?

The best way to draw a context map is by defining bounded contexts and mapping their strategic relationships, such as customer/supplier or shared kernel. This visualizes service boundaries and guides integration pattern selection for microservices.

How do I determine the Core Domain in a domain-driven design?

To determine the Core Domain in domain-driven design, you analyze your system's bounded contexts to identify the essential business value. This strategic DDD decision guides where to focus modeling efforts and team alignment.

Does strategic DDD help with integrating legacy systems?

Yes, strategic DDD helps with integrating legacy systems by validating boundaries and suggesting integration approaches like an Anticorruption Layer. It operates at the system level to guide how new and legacy architectures should relate.