microservice-splitting

What problem does it solve?

Prevents premature or risky microservice splits by evaluating whether the proposed boundary can be operated independently with clear data ownership, stable contracts, resilient failure handling, and non-lockstep deployment.

Core Features & Use Cases

• Microservice split readiness evaluation: Assesses ownership, deployment independence, observability maturity, contract versioning, and operational readiness before approving a boundary change.
• Anti-pattern detection and hard blocking rules: Rejects splits that rely on shared databases, missing contracts, undefined consistency strategies, weak failure handling, or absent ownership/on-call coverage.
• Actionable decision output: Produces an approve/reject/defer decision framework tied to concrete engineering requirements (timeouts, retries, circuit breakers, degradation behavior, Pact/CDCT readiness, and Saga/Outbox design).

Quick Start

Use the microservice-splitting skill to evaluate a proposed service boundary and ask it to produce an approve, reject, or defer decision with a scored readiness matrix and a concrete contract and consistency plan.