domain-identification-grouping

Group code components into logical business domains and produce domain maps.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill removes ambiguity about where code components belong by grouping them into logical, business-focused domains so teams can plan service extraction and align namespaces with business capabilities.

Core Features & Use Cases

  • Domain discovery: Analyze component responsibilities, vocabulary, and relationships to identify candidate business domains.
  • Component grouping & validation: Assign components to domains, check cohesion, and produce a validation checklist for stakeholder review.
  • Namespace refactoring & plans: Propose target namespaces, prioritize refactors, and create step-by-step migration guidance for service-based architecture.
  • Use case: Prepare a legacy monolith for migration by creating a domain map, listing misaligned namespaces, and outputting a prioritized refactoring plan to support domain services.

Quick Start

Group the project's components into logical business domains, produce a domain map, and suggest namespace refactoring steps.

Frequently Asked Questions about domain-identification-grouping

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

FAQPage Schema
How do I group components into business domains for service extraction?

To group components into business domains, analyze component responsibilities, vocabulary, and relationships to produce domain assignments and a domain map. This identifies logical boundaries for planning service-based architecture extraction and namespace refactoring.

What is the best way to map a legacy monolith to domains for a migration plan?

Mapping a legacy monolith to domains involves analyzing component relationships and vocabulary to create a domain map, listing misaligned namespaces, and outputting a prioritized refactoring plan to support domain services and migration.

Can I validate component grouping and domain cohesion before refactoring?

Yes, component grouping validation checks domain cohesion and produces a validation checklist for stakeholder review. This ensures logical business domain assignments are accurate before proceeding with namespace refactoring or service extraction.

How do I prepare a domain-driven design map from an existing codebase?

Preparing a domain-driven design map requires analyzing codebase component responsibilities and relationships to identify candidate business domains. The result is a structured domain map with assignments and refactoring plans.

Does domain identification work for planning microservices or only namespace refactoring?

Domain identification works for both microservices planning and namespace refactoring. It applies to codebase analysis and domain mapping when planning service extraction, producing domain assignments, validation checklists, and migration steps for service-based architecture.