What problem does it solve? Splitting a monolith without structural analysis leads to poorly bounded services, duplicated domain logic, and tangled coupling. This Skill runs a sequenced five-pattern analysis pipeline that inventories and sizes components, detects duplicated domain functionality, fixes hierarchy issues, measures coupling, and groups components into candidate domain-aligned units before any extraction begins. ## Core Features & Use Cases - Component Inventory & Sizing: Identifies leaf-node components, counts statements, and flags oversized or undersized components using percentage thresholds and standard deviation analysis. - Duplication & Coupling Analysis: Detects common domain functionality across components, assesses consolidation feasibility with afferent coupling metrics, and maps dependencies between modules. - Domain Grouping with DDD: Groups components into candidate domains and optionally applies strategic Domain-Driven Design analysis (subdomains, bounded contexts, ubiquitous language) via embedded reference guides. - Use Case: A team planning to break a large Node.js monolith into services asks the agent to run Patterns 1–5, receiving an evidence-backed report of component sizes, duplicated notification logic, coupling hotspots, and proposed service boundaries. ## Quick Start Ask the agent to run the full modular decomposition pipeline (Patterns 1 through 5) on your repository to inventory components, analyze coupling, and propose domain-aligned service groupings.
