ddd-strategic-design

Define DDD strategic artifacts including subdomains, bounded contexts, and ubiquitous language.

10|3|Updated Mar 14, 2025

Search Tags:#domain modeling #ddd #software architecture #strategic design #bounded context #ubiquitous language

Ready to run

npx skills add https://github.com/Mentor-Wizard/mentor-wizard-webapp --skill ddd-strategic-design-mentor-wizard

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ddd-strategic-design
Source: https://github.com/Mentor-Wizard/mentor-wizard-webapp/tree/main/.claude/skills/ddd-strategic-design
Command: npx skills add https://github.com/Mentor-Wizard/mentor-wizard-webapp --skill ddd-strategic-design-mentor-wizard

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps in defining the strategic architectural artifacts for complex business domains, enabling better organization, communication, and scalability by breaking down large systems into manageable parts.

Core Features & Use Cases

Subdomain Identification: Classify business capabilities into core, supporting, and generic subdomains.
Bounded Context Definition: Define clear boundaries for different parts of the system, aligning with team ownership and consistency.
Ubiquitous Language: Establish a shared vocabulary between technical and business stakeholders.
Use Case: When starting a new large-scale project or refactoring a monolith, use this skill to visually map out the different domains, their responsibilities, and how they interact, ensuring a common understanding across the team.

Quick Start

Use the ddd-strategic-design skill to map our commerce domain into bounded contexts, classify subdomains, and propose team ownership.

Frequently Asked Questions about ddd-strategic-design

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

FAQPage Schema

How do I split a monolith into bounded contexts?▼

To split a monolith into bounded contexts, map complex business domains into clear boundaries aligning with team ownership. This process defines domain boundaries and breaks large systems into manageable, consistent parts for better scalability.

What is a ubiquitous language in domain driven design?▼

Ubiquitous language in domain driven design establishes a shared vocabulary between technical and business stakeholders. It requires clear articulation of business capabilities to ensure common understanding across the team.

How do I identify core, supporting, and generic subdomains?▼

Identify core, supporting, and generic subdomains by classifying business capabilities according to their strategic value. This subdomain identification helps organize complex domains and define clear responsibilities for each bounded context.

When do I need strategic design for software architecture?▼

You need strategic design for software architecture when starting a new large-scale project or refactoring a monolith. It helps visually map domains, define boundaries, and establish relationships to ensure system scalability and communication.

Can I define team ownership using domain modeling?▼

Yes, you can define team ownership using domain modeling by aligning bounded context boundaries with specific team responsibilities. This ensures consistency within context limits and clarifies ownership over distinct business capabilities.