domain-driven-design

Plan domain-driven design decisions across strategic modeling and bounded contexts.

1|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/caobingsheng/skills --skill domain-driven-design-caobingsheng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: domain-driven-design
Source: https://github.com/caobingsheng/skills/tree/main/ddd/domain-driven-design
Command: npx skills add https://github.com/caobingsheng/skills --skill domain-driven-design-caobingsheng

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Domain-driven design planning helps teams define clear boundaries, shared language, and alignment between strategy and implementation, reducing integration risk and rework.

Core Features & Use Cases

  • Strategic modeling: identify subdomains, core vs supporting contexts, and ubiquitous language.
  • Context mapping and ownership: define bounded contexts, their owners, and integration contracts.
  • Routing to tactical patterns: map decisions to specialized skills like @ddd-tactical-patterns and @ddd-context-mapping.
  • Evidence-based planning: set up ADRs and success criteria for each phase.

Quick Start

Identify your core domain, map bounded contexts, and outline initial strategic artifacts to guide subsequent DDD activities.

Frequently Asked Questions about domain-driven-design

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

FAQPage Schema
How do I plan domain-driven design for complex business domains?

Plan domain-driven design by applying strategic modeling, defining bounded contexts, and routing tactical implementation to connect domain decisions to technical patterns. This process establishes explicit boundaries and ubiquitous language while reducing integration risk and rework.

What is strategic modeling in domain-driven design?

Strategic modeling in domain-driven design is the process of identifying subdomains, distinguishing core versus supporting contexts, and establishing a ubiquitous language to align strategy with implementation and define measurable milestones.

How do I define bounded contexts and context mapping ownership?

Define bounded contexts and context mapping ownership by outlining initial strategic artifacts that specify context boundaries, identify owners, and establish integration contracts to connect domain decisions to technical patterns.

When do I need domain-driven design planning?

You need domain-driven design planning when complex business domains require clear boundaries, shared language, and alignment between strategy and implementation to reduce integration risk and minimize rework.

How do I set up evidence-based planning for domain-driven design?

Set up evidence-based planning for domain-driven design by creating architecture decision records and defining success criteria for each phase, ensuring traceable decision records and measurable milestones throughout the delivery lifecycle.

Can I route domain-driven design decisions to specialized tactical patterns?

Yes, you can route domain-driven design decisions to specialized tactical patterns by mapping strategic decisions to specific skills, ensuring domain models connect effectively to technical implementation.