Software Development
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.
- Publisher / source
- mohitagw15856/pm-claude-skills (found on the CSV list)
- Upstream record
- mohitagw15856/pm-claude-skills
- Version
- Version 2
- Published
- Publication review
- Approved for publication · recorded passed scan 2026-11-03
- Content fingerprint
5160a26d9073011bc608ce0f952e950f4e2bc9ab645fa9de6c59f457f4ef2d7e