What problem does it solve? Splitting a monolith without structural analysis leads to poorly bounded services, hidden coupling, and duplicated domain logic. This Skill runs a sequenced five-pattern analysis pipeline that inventories and sizes components, finds duplicated domain functionality, fixes hierarchy problems, measures coupling, and groups components into candidate domain-aligned units before any extraction begins. ## Core Features & Use Cases - Component Inventory and Sizing: Identifies leaf-node components, counts statements, and flags oversized or undersized components using percentage thresholds and standard deviation analysis. - Duplication and 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 to validate bounded contexts and ubiquitous language. - Use Case: A team planning to break a large Node.js monolith into services runs the full Patterns 1-5 pipeline to get an evidence-based component inventory, coupling report, and domain grouping before writing any extraction roadmap. ## Quick Start Ask the agent to run modular decomposition Patterns 1 through 5 on your repository to inventory components, analyze coupling, and group modules into domains.
