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.

Install

npx pm-claude-skills add --agent claude   # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y pm-claude-skills-mcp

What to give it

• 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 characteristics, or scaling constraints per domain area
• Migration constraints — what cannot be rewritten all at once, hard deadlines, zero-downtime requirements, budget constraints
• Integration points — external systems, third-party APIs, or legacy systems that cannot be changed

Related skills