modular-decomposition
Runs a sequenced monolith-to-modular pipeline that sizes and inventories components, finds shared domain duplication, addresses flattening and hierarchy issues, analyzes coupling, then groups components into candidate domain-aligned units, with optional embedded DDD strategic analysis for bounded contexts. Use when asking how to split a monolith, size components before extraction, find duplicated domain logic, clean up module hierarchy, measure coupling between modules, or group components into services. Do NOT use for phased extraction roadmaps or prioritization without the prior analysis steps (use decomposition-planning-roadmap after this pipeline), end-to-end legacy migration strategy writeups (use legacy-migration-planner), pure infrastructure capacity sizing, or when you only need DDD without the structural pipeline (install domain-analysis standalone).
Best for Teams planning monolith dec…Works with GitHubLow risk
⌘source
- author
@tech-leads-club- language
- TypeScript
★2.1kstars
245forks
Apr 18, 2026
✦overview.md
Key Features
- ·Sizes and inventories components
- ·Finds shared domain duplication
- ·Addresses flattening and hierarchy issues
- ·Analyzes coupling between modules
- ·Groups components into candidate domain-aligned units
- ·Optional embedded DDD strategic analysis for bounded contexts
Use Cases
- →Splitting a monolith into services
- →Sizing components before extraction
- →Finding duplicated domain logic across modules
- →Cleaning up module hierarchy
- →Measuring coupling between modules
- →Grouping components into services
Best for
- ✓Teams planning monolith decomposition
- ✓Architects analyzing codebase structure
- ✓Developers preparing for service extraction
Not ideal for
- !Phased extraction roadmaps without prior analysis
- !End-to-end legacy migration strategy writeups
- !Pure infrastructure capacity sizing
- !DDD analysis without structural pipeline
FAQs
name
modular-decomposition
description
Runs a sequenced monolith-to-modular pipeline that sizes and inventories components, finds shared domain duplication, addresses flattening and hierarchy issues, analyzes coupling, then groups components into candidate domain-aligned units, with optional embedded DDD strategic analysis for bounded contexts. Use when asking how to split a monolith, size components before extraction, find duplicated domain logic, clean up module hierarchy, measure coupling between modules, or group components into services. Do NOT use for phased extraction roadmaps or prioritization without the prior analysis steps (use decomposition-planning-roadmap after this pipeline), end-to-end legacy migration strategy writeups (use legacy-migration-planner), pure infrastructure capacity sizing, or when you only need DDD without the structural pipeline (install domain-analysis standalone).
Modular Decomposition
This skill runs the Patterns 1–5 analysis pipeline before service extraction. Each pattern is plain markdown under references/; load the file for that step and execute it against the user’s codebase.
How to Use
Quick start (what users can say)
- Full pipeline: “Run modular decomposition Patterns 1 through 5 on this repo,” “Analyze this monolith for splitting—inventory, coupling, and domain grouping.”
- Single early step: “Identify and size components here,” “Find duplicated domain logic across modules,” “Analyze coupling between our packages.”
- With DDD lens: “Group components into domains and check bounded contexts,” “Use DDD strategic design on this codebase before we group services.”
If the user only wants extraction order, phases, or migration roadmap after analysis exists, use decomposition-planning-roadmap instead. If they need a full legacy migration plan (strangler fig, research, multi-stack), use legacy-migration-planner as well or instead of this skill when that is the primary ask.
How the agent should run it
$install
1-click copynpx skills add tech-leads-club/agent-skills --skill modular-decompositionSafety assessment
★
Clarity score
How clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
3/ 5
goodMostly clear, but there are still a few confusing or poorly structured parts.
◎
Actionability score
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
3/ 5
mediumPartially actionable with several concrete steps, but still missing important details.