ddd-strategic-design

Map business domains into subdomains, bounded contexts, and a glossary.

10|Updated May 20, 2026
One-click install
npx skills add https://github.com/AI-Safeter/antigravity-cli-plugin --skill ddd-strategic-design-ai-safeter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ddd-strategic-design
Source: https://github.com/AI-Safeter/antigravity-cli-plugin/tree/main/plugins/ddd-strategic-design
Command: npx skills add https://github.com/AI-Safeter/antigravity-cli-plugin --skill ddd-strategic-design-ai-safeter

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

DDD strategic design helps teams identify core, supporting, and generic subdomains, define bounded contexts, and establish a shared ubiquitous language to align stakeholders in complex business domains.

Core Features & Use Cases

  • Map business capabilities to subdomains and bounded contexts to clarify ownership and boundaries.
  • Create a ubiquitous language glossary and ADRs to capture design decisions and rationale.
  • Provide templates and guidelines to structure strategic design work and drive consensus across teams.

Quick Start

Describe your domain landscape and run the strategic design workflow to produce subdomain classifications, bounded contexts, and a glossary.

Frequently Asked Questions about ddd-strategic-design

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

FAQPage Schema
How do I map complex business domains into bounded contexts and subdomains?

To map complex business domains, you classify subdomains as core, supporting, or generic, and define bounded contexts to clarify ownership and boundaries across multiple teams. This strategic domain decomposition aligns stakeholders and structures complex business landscapes.

What is a ubiquitous language glossary and when do I need it for domain-driven design?

A ubiquitous language glossary is a shared vocabulary created during strategic domain-driven design to align stakeholders. You need it when mapping complex business domains to ensure consistent communication across multiple teams and bounded contexts.

How do I capture architectural decisions for bounded context boundaries?

You capture architectural decisions for bounded context boundaries using Architecture Decision Records, or ADRs. These records document the rationale behind context boundary decisions and subdomain classifications, driving consensus across multiple teams.

Can I use strategic domain-driven design for domain decomposition across multiple teams?

Yes, strategic domain-driven design applies directly to engagements requiring domain decomposition across multiple teams. It maps business capabilities to bounded contexts, clarifies ownership boundaries, and provides templates to drive stakeholder consensus.

What is the best way to establish a shared ubiquitous language across stakeholders?

The best way to establish a shared ubiquitous language is by creating a glossary through strategic domain-driven design. This maps business capabilities to subdomains and bounded contexts, aligning stakeholders and capturing design decisions in templates.

Why does my team struggle with ownership boundaries in complex business domains?

Teams struggle with ownership boundaries when complex business domains lack defined bounded contexts. Mapping business capabilities to subdomains and establishing a ubiquitous language clarifies boundaries, ownership, and aligns stakeholders across multiple teams.