domain-analysis

Identify subdomains and map bounded contexts in codebases.

1|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/marcius-llmus/skills --skill domain-analysis-marcius-llmus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: domain-analysis
Source: https://github.com/marcius-llmus/skills/tree/main/%28architecture%29/domain-analysis
Command: npx skills add https://github.com/marcius-llmus/skills --skill domain-analysis-marcius-llmus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps software teams discover and clarify domain boundaries by extracting business concepts from code, grouping them by ubiquitous language, scoring internal cohesion, and revealing harmful coupling so teams can design clear bounded contexts for Domain-Driven Design and refactoring.

Core Features & Use Cases

  • Concept Extraction: Finds entities, services, use cases, and entry points across a repository to surface business concepts.
  • Subdomain Classification & Cohesion: Groups concepts by vocabulary, classifies subdomains as Core/Supporting/Generic, and computes cohesion scores with rationale.
  • Bounded Context Mapping & Recommendations: Produces domain maps, cohesion matrices, low-cohesion reports, and integration pattern suggestions to guide architectural changes.
  • Use Case Example: Analyze a monolith to separate Billing (supporting) from Identity (generic) and propose events or API contracts to decouple them.

Quick Start

Analyze this repository and return identified subdomains, cohesion scores, and suggested bounded contexts.

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 an existing codebase?

To identify bounded contexts and subdomains, extract business concepts like entities and services from your repository, group them by ubiquitous language, and classify them as Core, Supporting, or Generic subdomains to map clear architectural boundaries.

What is domain-driven design strategic analysis and when do I need it for refactoring?

Domain-driven design strategic analysis maps subdomains and bounded contexts to surface coupling issues and assess cohesion. You need it for refactoring planning when separating monolithic modules into decoupled domains using integration patterns like events or API contracts.

How can I measure codebase cohesion to find harmful coupling between modules?

You can measure codebase cohesion by computing cohesion scores for grouped business concepts to generate a cohesion matrix. This process surfaces harmful coupling issues and produces low-cohesion reports to guide your architectural refactoring.

Can I analyze any repository to extract business concepts for DDD?

Yes, you can apply domain analysis to any repository or module to extract business concepts, find entry points and use cases, and group vocabulary to produce domain maps suitable for Domain-Driven Design.

What is the best way to separate a monolith into bounded contexts?

The best way to separate a monolith into bounded contexts is to extract business concepts, classify subdomains by cohesion, and use the resulting domain maps and integration pattern suggestions to decouple modules like Billing and Identity.

Why does my subdomain classification show low cohesion and what should I do?

Low cohesion in subdomain classification indicates harmful coupling or misgrouped ubiquitous language. You should review the low-cohesion reports to refactor business concepts into clearer bounded contexts and apply recommended integration patterns.