skills.rest
rafael-hc
rafael-hcCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

domain-analysis

Identifies subdomains and suggests bounded contexts from codebase analysis.

Updated Mar 11, 2026
Search Tags:#domain modeling#ddd#strategic design#codebase analysis#bounded contexts#subdomain analysis
One-click install
npx skills add https://github.com/rafael-hc/AoPonto-FoodService --skill domain-analysis-rafael-hc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: domain-analysis
Source: https://github.com/rafael-hc/AoPonto-FoodService/tree/main/.agents/skills/domain-analysis
Command: npx skills add https://github.com/rafael-hc/AoPonto-FoodService --skill domain-analysis-rafael-hc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the complex and often ambiguous task of identifying distinct business domains and suggesting clear boundaries for them within any codebase, ensuring better alignment between software architecture and business strategy.

Core Features & Use Cases

  • Subdomain Identification: Classifies business capabilities into Core, Supporting, or Generic domains.
  • Bounded Context Suggestion: Proposes explicit linguistic boundaries for services and modules.
  • Cohesion Analysis: Assesses the interconnectedness of concepts within and across domains.
  • Use Case: When refactoring a monolith into microservices, this Skill helps determine the optimal domain boundaries for each new service, preventing the creation of a distributed monolith.

Quick Start

Analyze the domains in this codebase and suggest bounded contexts.

Frequently Asked Questions about domain-analysis

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

FAQPage Schema
What is subdomain analysis in Domain-Driven Design and how does it classify business capabilities?▼

Subdomain analysis in Domain-Driven Design classifies business capabilities into Core, Supporting, or Generic domains. It extracts business concepts from the codebase and groups them by ubiquitous language to determine strategic business value.

Why does low cohesion cause a distributed monolith when separating microservices?▼

Low cohesion causes a distributed monolith because tightly coupled business concepts retain underlying dependencies even after separation. Assessing interconnectedness through a cohesion matrix prevents this by recommending optimal domain boundaries before splitting services.

What is the best way to analyze a codebase for Domain-Driven Design strategic design boundaries?▼

The best way to analyze a codebase for Domain-Driven Design strategic design boundaries is to extract business concepts, group them by ubiquitous language, and assess their interconnectedness. This generates domain maps and cohesion matrices for optimal separation.

When do I need a cohesion matrix for assessing domain boundaries?▼

A cohesion matrix is needed when assessing domain boundaries to evaluate the interconnectedness of concepts within and across subdomains. It detects low cohesion issues and provides actionable recommendations for separating Core, Supporting, and Generic domains.

Related Skills

Explore More Software Engineering Skills→
safzanpiranisafzanpirani
1

ubiquitous-language

Extract domain terms and flag ambiguities from conversations into a glossary.

Community
Intermediate
rodrigotoledorodrigotoledo

domain-analysis

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

Community
Advanced
radkomihradkomih

ddd-refactor

Analyze codebases to identify DDD anti-patterns and generate a phased refactoring plan.

Community
Advanced
agnaldo4jagnaldo4j
1

circular-dependency-control

Detect and classify circular dependencies across Kotlin class, package, and Gradle module boundaries.

Community
Advanced