ddd-strategic-design

Maps business capabilities into subdomains and bounded contexts with glossary terms and rationale.

Updated May 5, 2026
One-click install
npx skills add https://github.com/Movchanets/Microservices_Learning --skill ddd-strategic-design-movchanets
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ddd-strategic-design
Source: https://github.com/Movchanets/Microservices_Learning/tree/main/.agents/skills/ddd-strategic-design
Command: npx skills add https://github.com/Movchanets/Microservices_Learning --skill ddd-strategic-design-movchanets

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams break a complex business domain into clear subdomains and bounded contexts so architecture, ownership, and language stay aligned.

Core Features & Use Cases

  • Subdomain Classification: Identify core, supporting, and generic subdomains from business capabilities.
  • Bounded Context Design: Define ownership boundaries, upstream and downstream relationships, and context responsibilities.
  • Ubiquitous Language: Build a shared glossary of canonical terms and anti-terms to reduce ambiguity across teams.
  • Use Case: A team planning a microservices platform can use this Skill to map business capabilities, align services to contexts, and document the strategic decisions before implementation.

Quick Start

Ask the ddd-strategic-design skill to analyze a business domain and produce subdomain, bounded context, and glossary recommendations.

Frequently Asked Questions about ddd-strategic-design

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

FAQPage Schema
How do I decompose a complex business domain into subdomains and bounded contexts?▼

Strategic design in DDD solves domain decomposition by mapping business capabilities into classified subdomains and bounded contexts, establishing clear ownership boundaries, upstream/downstream relationships, and ubiquitous language to align architecture and teams.

What is a ubiquitous language glossary and when do I need one for domain modeling?▼

A ubiquitous language glossary is a shared vocabulary of canonical terms and anti-terms that reduces ambiguity across teams. You need one during domain modeling to align language within bounded contexts for complex business systems.

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

Identify core, supporting, and generic subdomains by analyzing a capability inventory to classify business capabilities based on competitive differentiation and business value, guiding architectural boundaries and team ownership alignment.

Can I use strategic design to align team ownership for a microservices platform?▼

Yes, strategic design aligns team ownership for a microservices platform by mapping business capabilities to bounded contexts, defining clear service boundaries, context responsibilities, and upstream/downstream relationships before implementation.

What inputs do I need to design bounded contexts and subdomain classifications?▼

Designing bounded contexts and subdomain classifications requires a capability inventory, context boundaries, glossary terms, and rationale for strategic design decisions to effectively map and decompose the business domain.

Why define upstream and downstream relationships when mapping bounded contexts?▼

Defining upstream and downstream relationships when mapping bounded contexts clarifies context responsibilities and team ownership dependencies, ensuring aligned architecture and controlled communication flows between complex business system boundaries.