# Multi Service Orchestration

PM2 process management, backend/frontend cascade execution, parallel worktree builds...

- Repository: https://github.com/a5c-ai/babysitter (1887 stars)
- Category: Design
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add a5c-ai/babysitter --skill multi-service-orchestration -g -a claude-code -y`
Codex: `npx skills add a5c-ai/babysitter --skill multi-service-orchestration -g -a codex -y`
Cursor: `npx skills add a5c-ai/babysitter --skill multi-service-orchestration -g -a cursor -y`
Gemini CLI: `npx skills add a5c-ai/babysitter --skill multi-service-orchestration -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add a5c-ai/babysitter`

## Description

PM2 process management, backend/frontend cascade execution, parallel worktree builds, and cross-service integration testing.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

- Scan for service directories (packages/, services/, apps/)
- Parse package.json for dependencies and scripts
- Build dependency graph
- Detect package managers per service
- Determine topological execution order
- Flag circular dependencies

## Execution Modes

### Cascade Mode
- Sequential execution following dependency order
- Wait for health check before starting dependents
- Stop on failure with detailed error report
- Support partial cascade (skip healthy services)

### Parallel Mode
- Concurrent execution for independent services
- Optional worktree isolation per service
- Configurable concurrency limit
- Collect all results (continue on individual failures)

### Auto Mode (Default)
- Analyze dependency graph
- Use cascade for services with sequential dependencies
- Use parallel for independent service groups
- Hybrid: cascade between groups, parallel within groups

## PM2 Management
- Generate ecosystem.config.js from service manifest
- Configure per service: name, script, cwd, env, instances
- Start in topological order with health check gates
- Log rotation and restart policies
- Status monitoring: online, stopped, errored

## Cross-Service Testing
- API contract verification (request/response schemas)
- Event bus message flow testing
- Shared state consistency checks
- Authentication across service boundaries
- Circuit breaker behavior validation

## Health Monitoring
- Health check endpoint polling
- PM2 process status monitoring
- Resource usage tracking (CPU, memory)
- Log file error pattern detection
- Inter-service connectivity verification

## When to Use

- Multi-package monorepo development
- Microservice orchestration
- Full-stack application management
- CI/CD pipeline for multi-service deployments

## Agents Used

- `architect` (service discovery and dependency mapping)
- `build-resolver` (individual service builds)
- `e2e-runner` (cross-service integration testing)