OpenParable
Skip to content
← Back to skills

Multi Service Orchestration

DevOps & Security
multi-service-orchestration

Multi Service Orchestration is an Agent Skill for devops & security published in the a5c-ai/babysitter repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/a5c-ai/babysitter/blob/HEAD/library/methodologies/everything-claude-code/skills/multi-service-orchestration/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/multi-service-orchestration, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

  • 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)