microservices-decomposition
Design a microservices decomposition for a monolith or new system, defining service boundaries, ownership, communication patterns, and migration plan. Use when asked to decompose a monolith, define service boundaries, design a microservices architecture, or plan a strangler-fig migration. Produces a bounded context map, service inventory table, communication pattern decisions, data ownership matrix, migration roadmap, and risk register.
npx skills add mohitagw15856/pm-claude-skills --skill microservices-decomposition --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Microservices Decomposition Produce a complete microservices decomposition design for a system — whether decomposing an existing monolith or designing service boundaries for a new system. Ground the decomposition in Domain-Driven Design (DDD) concepts: identify bounded contexts first, then derive service boundaries from them. Include communication pattern decisions (sync vs. async, event vs. RPC), data ownership rules, and a pragmatic migration plan if decomposing a monolith. Conway's Law is real — include an organizational alignment section. The deliverable should be specific enough that a team can begin implementation, not an abstract architectural diagram. ## Required Inputs Ask for these if not already provided: - **System or domain description** — what the system does, its core domain, and the key business processes it supports - **Current architecture** — monolith (describe the tech stack and rough module structure), partial services (list existing services), or greenfield - **Team structure** — number of teams, team names if known, and approximate team sizes; this drives service ownership - **Performance and scalability requirements** — any specific SLAs, load characterist
- Required Inputs
- Output Format
- 1. Domain Analysis
- Core Domain
- Domain Map
- 2. Bounded Context Map (ASCII)
- Context Relationships
- 3. Proposed Service Inventory
- Service Responsibility Rules (applied to every service above)
- 4. Inter-Service Communication Patterns
- Pattern Decision Matrix
- Per-Service Communication Decisions
- Event Catalog
- 5. Data Ownership Matrix
What does the microservices-decomposition skill do?
Design a microservices decomposition for a monolith or new system, defining service boundaries, ownership, communication patterns, and migration plan. Use when asked to decompose a monolith, define service boundaries, design a microservices architecture, or plan a strangler-fig migration. Produces a bounded context map, service inventory table, communication pattern decisions, data ownership matrix, migration roadmap, and risk register.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill microservices-decomposition --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.