Verified:GitHub

domain-analysis

Identify business subdomains and propose bounded contexts with cohesion scores.

Updated Aug 27, 2026

Search Tags:#domain modeling #ddd #bounded context #ubiquitous language #service boundaries #architecture refactoring #cohesion scoring

Ready to run

npx skills add https://github.com/luizgmassa/Useful-Agent-Skills --skill domain-analysis-luizgmassa

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: domain-analysis
Source: https://github.com/luizgmassa/Useful-Agent-Skills/tree/main/skills/domain-analysis
Command: npx skills add https://github.com/luizgmassa/Useful-Agent-Skills --skill domain-analysis-luizgmassa

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you identify business subdomains and draw bounded context boundaries in an existing codebase, so your architecture matches the underlying domain language instead of drifting into mixed responsibilities.

Core Features & Use Cases

Extracts business concepts from entities, services, use cases, and entry points to build a domain inventory.
Groups by ubiquitous language to detect where the same term means different things across the system.
Classifies subdomains (Core/Supporting/Generic) and assesses cohesion using a structured scoring model, then reports low-cohesion and coupling risks with recommendations.

Quick Start

Ask: "Analyze this codebase and suggest subdomains and bounded contexts, including cohesion scores and any low-cohesion/coupling issues."

Frequently Asked Questions about domain-analysis

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

FAQPage Schema

How do I identify bounded contexts and subdomains in a legacy codebase?▼

To identify bounded contexts in a legacy codebase, extract business concepts from entities and services, group them by ubiquitous language, and classify them as Core, Supporting, or Generic subdomains to reveal natural boundaries.

What is domain-driven refactoring and when do I need to evaluate service boundaries?▼

Domain-driven refactoring restructures code to align with business capabilities, requiring service boundary evaluation when mixed responsibilities and low cohesion cause coupling risks that drift away from the ubiquitous domain language.

How can I calculate a cohesion matrix to detect low-cohesion bounded contexts?▼

Calculate a cohesion matrix by scanning business concepts, grouping them by ubiquitous language, and scoring their relationships to detect low-cohesion bounded contexts and coupling risks, which outputs actionable separation recommendations.

Does this approach work for planning architecture refactoring in a new codebase?▼

Yes, you can apply this to a new codebase by mapping domains to extract business concepts, classifying subdomains, and assessing cohesion to ensure initial service boundaries align directly with business capabilities.

What is the best way to separate coupled subdomains and fix low-cohesion boundaries?▼

The best way to fix low-cohesion boundaries is to compute a cohesion matrix, classify subdomains, and output actionable separation recommendations with integration patterns to resolve coupling risks between mismatched contexts.

Why does the same ubiquitous language term mean different things across my system?▼

Terms in your ubiquitous language mean different things when business concepts are scattered across mixed responsibilities, requiring grouping by language to detect these overlaps and propose proper bounded contexts.