multi-service-orchestration

name	multi-service-orchestration
description	PM2 process management, backend/frontend cascade execution, parallel worktree builds, and cross-service integration testing.
allowed-tools	Read, Write, Edit, Bash, Grep, Glob
graph	{"domains":["domain:software-engineering"],"skillAreas":["skill-area:agentic-loops","skill-area:orchestration-loop"],"workflows":["workflow:feature-development"],"topics":["topic:developer-experience"],"roles":["role:tech-lead","role:backend-engineer"]}

• 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