ddd-strategic-design

Analyze business domains into subdomains, bounded contexts, and ubiquitous language artifacts.

41|5|Updated Sep 30, 2025
One-click install
npx skills add https://github.com/efekrbas/discord-hypesquad-manager --skill ddd-strategic-design-efekrbas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ddd-strategic-design
Source: https://github.com/efekrbas/discord-hypesquad-manager/tree/main/.agents/skills/ddd-strategic-design
Command: npx skills add https://github.com/efekrbas/discord-hypesquad-manager --skill ddd-strategic-design-efekrbas

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, bounded contexts, and shared language before implementation, reducing ambiguity and ownership confusion.

Core Features & Use Cases

  • Subdomain classification: Distinguish core, supporting, and generic areas.
  • Bounded context design: Define responsibilities, boundaries, and dependencies.
  • Ubiquitous language: Build a glossary and anti-terms for alignment across teams.
  • Use case: Plan a commerce platform by separating pricing, checkout, catalog, and identity into coherent contexts with clear ownership.

Quick Start

Ask the skill to analyze your domain and produce subdomain classifications, bounded contexts, and a ubiquitous language glossary for your system.

Frequently Asked Questions about ddd-strategic-design

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

FAQPage Schema
How do I break a complex business domain into bounded contexts?

To break a complex business domain into bounded contexts, you classify subdomains into core, supporting, and generic areas, define responsibilities and dependencies, and build a ubiquitous language glossary for team alignment.

What is ubiquitous language in domain-driven design?

Ubiquitous language in domain-driven design is a normalized glossary and anti-terms list shared across teams to ensure semantic alignment and reduce ambiguity within specific bounded contexts.

How do I classify subdomains when decomposing a legacy monolith?

Classifying subdomains when decomposing a legacy monolith involves distinguishing core, supporting, and generic areas to map context boundaries, clarify team ownership, and plan implementation handoff.

Can I use strategic domain design to align team ownership for a new system?

Yes, strategic domain design aligns team ownership for new systems by mapping bounded context boundaries and dependencies, producing rationale suitable for architecture decision records and implementation handoff.

When do I need to map bounded contexts for a commerce platform?

You need to map bounded contexts for a commerce platform when separating pricing, checkout, catalog, and identity into coherent areas with clear responsibilities to prevent ownership confusion and ambiguity.