All skills
microservice-splitting
FoundationJIT onlyanalysis-agent/task-agent/review-agent: use when a service split affects ownership, deployment, scaling, isolation, contracts, or data; skip without a split decision.
- Group
- Architecture & design
- Supported roles
- MainAnalysisTaskReview
- Source
- SKILL.md
Use when
Trigger signals that make this skill the right owner
- evaluate service split boundaries ownership deployment data and operational cost
Do not use when
Anti-triggers — as binding as the triggers above
- no task-local microservice splitting decision is required
Required inputs
What must be supplied before this skill can decide anything
- current task contract
- selected primary Professional Skill
- task-local trigger evidence
Output contract
What this skill owes the next role
- service split decision to approve, reject, or defer with business and runtime boundaries; code, data, contract, release, and incident ownership; source-of-truth and consistency authority; and dependency and contract transitions. The decision includes phased migration, mixed-version behavior, rollback, retirement, and exit conditions; failure-isolation and operability readiness; validation evidence and proof limits; rejection/defer reasons; and residual owners
Escalation signals
When this skill must hand the decision back
- Poor splits create distributed transactions and coordination overhead
Loaded by
This skill never owns a task. These professionals may pull it in as Layer 3.
Targeted references
Each reference carries its own load condition. None of them enter context by default.
| Reference | Load when | Do not load when | Required by |
|---|---|---|---|
| benchmarks-and-patterns.mdbenchmark-pattern | ownership scaling consistency or deployment forces leave extraction options viable | modular-monolith repair satisfies every material split force | AnalysisTaskReview |
| checklist.mddecision-checklist | extraction changes data ownership contracts transactions operations or release independence | no independently deployed service boundary is proposed | AnalysisTaskReview |
| evidence-patterns.mdevidence-pattern | split independence compatibility or operability claims need current proof | current topology contracts owners and validation prove each claim | AnalysisTaskReview |