domain-analysis

Identifies subdomains and bounded contexts in a codebase using DDD strategic design.

Updated Jun 18, 2026
One-click install
npx skills add https://github.com/rodrigotoledo/trading-exchange --skill domain-analysis-rodrigotoledo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: domain-analysis
Source: https://github.com/rodrigotoledo/trading-exchange/tree/main/packages/skills-catalog/skills/%28architecture%29/domain-analysis
Command: npx skills add https://github.com/rodrigotoledo/trading-exchange --skill domain-analysis-rodrigotoledo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams identify subdomains and map bounded contexts in a codebase using Domain-Driven Design (DDD) strategic design, enabling clearer linguistic boundaries and more cohesive architectures.

Core Features & Use Cases

  • Identify subdomains (Core, Supporting, Generic) from business concepts (entities, services, use cases, controllers)
  • Map to bounded contexts with explicit language boundaries
  • Assess cross-domain cohesion and surface integration patterns
  • Generate domain maps, cohesion matrices, and low-cohesion reports for actionable refactoring
  • Provide framework-agnostic guidance suitable for monoliths, microservices, or hybrid architectures

Quick Start

Analyze the codebase to identify subdomains, classify them as Core/Supporting/Generic, and propose bounded contexts using the six-phase DDD framework.

Frequently Asked Questions about domain-analysis

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

FAQPage Schema
How do I identify subdomains and bounded contexts in a codebase using DDD?▼

To identify subdomains using DDD, you analyze codebase entities, services, and controllers to classify them as Core, Supporting, or Generic. This process applies linguistic boundaries to assess cross-domain cohesion and generates domain maps for actionable refactoring.

What is the best way to map bounded contexts in a monolith?▼

Mapping bounded contexts in a monolith requires assessing cross-domain cohesion and surfacing integration patterns among business concepts. This approach produces cohesion matrices and low-cohesion reports to guide domain segmentation and refactoring.

Can I use strategic Domain-Driven Design to detect low cohesion in microservices?▼

Yes, strategic Domain-Driven Design detects low cohesion in microservices by analyzing linguistic boundaries and integration patterns. It classifies subdomains from business concepts and highlights low-cohesion areas to guide architectural refactoring across distributed systems.

When do I need a cohesion matrix for domain segmentation?▼

You need a cohesion matrix for domain segmentation when evaluating cross-domain integration patterns and linguistic boundaries in a codebase. It surfaces low-cohesion areas among subdomains, providing actionable recommendations for defining bounded contexts.

Does domain analysis for bounded contexts work with hybrid architectures?▼

Yes, domain analysis for bounded contexts works with hybrid architectures because it provides framework-agnostic guidance. It assesses cross-domain cohesion and applies linguistic boundaries to map subdomains regardless of whether the system is a monolith, microservices, or hybrid.