domain-analysis

Analyze codebases to identify subdomains and suggest bounded contexts.

Updated Feb 14, 2026
One-click install
npx skills add https://github.com/P4rzi/PROT-RISK --skill domain-analysis-p4rzi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: domain-analysis
Source: https://github.com/P4rzi/PROT-RISK/tree/main/.github/skills/domain-analysis
Command: npx skills add https://github.com/P4rzi/PROT-RISK --skill domain-analysis-p4rzi

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps you understand the business domains within any codebase, identify core business capabilities, and define clear boundaries for services and modules, preventing architectural sprawl and improving maintainability.

Core Features & Use Cases

  • Domain Identification: Classifies business capabilities into Core, Supporting, or Generic subdomains.
  • Bounded Context Suggestion: Proposes clear linguistic boundaries for services based on Ubiquitous Language.
  • Cohesion Analysis: Assesses the strength of relationships within and between domains.
  • Use Case: When refactoring a monolith into microservices, use this Skill to determine the optimal boundaries for each new service, ensuring each service owns a distinct business capability and language.

Quick Start

Analyze the domains in my 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
How do I identify bounded contexts and subdomains in my codebase?

To identify bounded contexts and subdomains in a codebase, this Skill analyzes business concepts and groups them by Ubiquitous Language using DDD Strategic Design principles. It classifies subdomains into Core, Supporting, or Generic categories to define clear service boundaries.

What is the best way to draw service boundaries when refactoring a monolith?

The best way to draw service boundaries when refactoring a monolith is assessing domain cohesion and mapping Ubiquitous Language. This Skill extracts business capabilities and suggests bounded contexts with integration patterns to prevent architectural sprawl and improve maintainability.

How does DDD strategic design map domains from existing source code?

DDD strategic design maps domains from source code by extracting business concepts and grouping them by their Ubiquitous Language. The analysis assesses relationship strength within and between domains to detect low cohesion issues and propose clear linguistic boundaries.

Can I detect low cohesion issues between business domains during codebase analysis?

Yes, you can detect low cohesion issues during codebase analysis. This Skill assesses the strength of relationships within and between domains, identifying low cohesion to help you properly separate bounded contexts and map appropriate integration patterns.

Do I need a specific framework to classify Core, Supporting, and Generic subdomains?

No specific framework is needed to classify Core, Supporting, and Generic subdomains. This Skill analyzes your codebase directly to identify business capabilities and categorize them using DDD Strategic Design principles without requiring external dependencies.

Why does my microservices architecture have linguistic conflicts between modules?

Microservices architecture has linguistic conflicts when bounded contexts overlap. This Skill extracts business concepts and groups them by Ubiquitous Language to detect low cohesion issues, ensuring each service owns a distinct business capability and language.