domain-analysis

Analyzes repositories to identify strategic groups and propose architectural blueprints and migrations.

98|25|Updated Mar 14, 2020

Search Tags:#architecture #domain-driven-design #bounded-context #domain-analysis #subdomain

Ready to run

npx skills add https://github.com/baotoq/micro-commerce --skill domain-analysis-baotoq

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: domain-analysis
Source: https://github.com/baotoq/micro-commerce/tree/main/.agents/skills/domain-analysis
Command: npx skills add https://github.com/baotoq/micro-commerce --skill domain-analysis-baotoq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identifies and organizes the core, supporting, and generic subdomains in a codebase and maps them to explicit bounded contexts using Domain-Driven Design principles.

Core Features & Use Cases

Extracts business concepts (entities, services, use cases) and groups them by ubiquitous language to reveal subdomain structure.
Proposes bounded contexts with linguistic boundaries, integration patterns, and cohesion guidance for refactoring or new architecture.
Provides a cohesive analysis template to assess boundaries, dependencies, and potential cross-domain issues.
Useful for legacy monoliths, microservices decomposition, or strategic design discussions with stakeholders.

Quick Start

Run a structured domain analysis on a target repository to map its problem space to solution space and present a bounded-context map.

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 monolith?▼

To identify bounded contexts and subdomains in a legacy monolith, extract business concepts and group them by ubiquitous language. This reveals the domain structure and proposes clear linguistic boundaries for refactoring.

What is domain-driven design strategic design for mapping software architectures?▼

Domain-driven design strategic design maps domain strategies to software architectures by classifying Core, Supporting, and Generic subdomains. It extracts ubiquitous language to propose integration points and guide structural planning.

How do I decompose microservices using domain analysis and cohesion analysis?▼

Decompose microservices using domain analysis by assessing boundaries and dependencies through cohesion analysis. This classifies subdomains and outlines clear integration points to align bounded contexts with the new architecture.

Can I use domain analysis for strategic design discussions with stakeholders on any size codebase?▼

Yes, you can use domain analysis for strategic design discussions with stakeholders on codebases of any size. It maps the problem space to the solution space and presents a bounded-context map for alignment.

When should I not use domain analysis for domain-driven refactoring?▼

Avoid domain analysis for domain-driven refactoring when your codebase lacks distinct ubiquitous language or clear business concepts. Without recognizable subdomain structure, extracting linguistic boundaries and integration points becomes ineffective.