ddd-subdomains

Classifies business capabilities into Core, Supporting, and Generic DDD subdomains with ownership recommendations.

Updated Jul 4, 2026
One-click install
npx skills add https://github.com/100Thieves-team/plady-expert-skills --skill ddd-subdomains-100thieves-team
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ddd-subdomains
Source: https://github.com/100Thieves-team/plady-expert-skills/tree/main/.claude/skills/ddd-subdomains
Command: npx skills add https://github.com/100Thieves-team/plady-expert-skills --skill ddd-subdomains-100thieves-team

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams doing strategic Domain-Driven Design often struggle to decide which parts of the business deserve custom investment and which should be bought or reused. This Skill turns raw event flows and boundary clues into a defensible subdomain classification with a core domain declaration. ## Core Features & Use Cases - Capability Extraction and Annotation: Extracts business capabilities from event flows, deduplicates synonyms, and annotates business value, complexity, change frequency, and external dependencies. - Subdomain Classification: Classifies capabilities as Core, Supporting, or Generic with rationale and suggested investment levels. - Core Domain Declaration and Ownership: Produces a one-page core domain declaration with measurable indicators plus team ownership and cross-team collaboration recommendations. - Use Case: After running domain discovery on an e-commerce platform, feed the event flows into this Skill to identify that pricing optimization is the Core subdomain while notifications and reporting are Generic, then hand the boundary candidates to context mapping. ## Quick Start Ask the assistant to classify subdomains by pasting the event flow table and boundary clues from ddd-discover and requesting the capability list, classification table, core domain declaration, and ownership recommendations.

Frequently Asked Questions about ddd-subdomains

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

FAQPage Schema
How do I identify core subdomains in domain-driven design?

Extract business capabilities from event flows, annotate each with business value, complexity, and change frequency, then classify differentiating capabilities as Core. Keep core subdomains to at most one third of the total and document measurable business indicators in a core domain declaration.

What is the difference between Core, Supporting, and Generic subdomains?

Core subdomains provide differentiating competitive advantage and deserve custom investment. Supporting subdomains are necessary but non-differentiating, while Generic subdomains are general-purpose capabilities that can be purchased or reused.

What inputs are required before classifying DDD subdomains?

You need event flows, command/event candidates, and boundary clues from a prior domain discovery step such as ddd-discover. Optional inputs include a current capability inventory and business differentiation hypotheses from scoping.

When should subdomain classification be redone?

Reclassify when context mapping reports a god context or circular dependencies, since these signal misclassification. Also backtrack to scoping if every capability appears equally important and Core cannot be distinguished from Supporting.

How many core subdomains should a system have?

Core subdomains should not exceed one third of the total subdomain count. An excessive number of core domains dilutes focus and indicates the classification needs revision.