parallel-orchestration
The parallel-orchestration skill coordinates multiple specialized agents across concurrent work streams for software development tasks, dispatching database engineers, API developers, UI developers, test engineers, and documentation writers based on task requirements. Use it when decomposed tasks need simultaneous execution with quality gates, cross-stream conflict detection, and integrated result merging to maintain consistency across parallel development efforts.
git clone --depth 1 https://github.com/a5c-ai/babysitter /tmp/parallel-orchestration && cp -r /tmp/parallel-orchestration/library/methodologies/ccpm/skills/parallel-orchestration ~/.claude/skills/parallel-orchestrationSKILL.md
# Parallel Orchestration Coordinate multiple specialized agents across parallel work streams with quality gates and conflict resolution. ## Agents - Database Engineer - `database-engineer` - API Developer - `api-developer` - UI Developer - `ui-developer` - Test Engineer - `test-engineer` - Documentation Writer - `documentation-writer` ## Workflow 1. Prepare execution plan with stream batches 2. Dispatch specialized agents per stream (ctx.parallel.all) 3. Execute tasks sequentially within each stream 4. Quality gate after each task with convergence loop (max 3 iterations) 5. Check for cross-stream conflicts 6. Resolve conflicts if found 7. Run integration verification 8. Merge stream results ## Inputs - `tasks` - Tasks from decomposition phase - `streams` - Work stream definitions - `qualityThreshold` - Minimum quality score (default: 80) - `maxParallel` - Maximum parallel streams (default: 5) - `githubRepo` - GitHub repo for progress sync (optional) ## Outputs - Per-stream execution results - Integration verification report - Conflict detection and resolution report - Merge result ## Agent Dispatch (5-12 parallel agents per issue) Agents are dispatched based on stream type: - `database` -> `database-engineer` - `api` -> `api-developer` - `ui` -> `ui-developer` - `testing` -> `test-engineer` - `docs` -> `documentation-writer` - `infrastructure` -> `architect` ## Process Files - `ccpm-parallel-execution.js` - Standalone parallel execution - `ccpm-orchestrator.js` - Phase 5 of full lifecycle
Coordinate Crew (persistent) and Polecat (transient) agents using Gas Town's hook-based work distribution and GUPP principle.
System and API design guidance covering component boundaries, data flow, integration patterns, and scalability considerations.
This skill should be used when the user asks to "find skills in the wild", "assimilate popular workflows", "discover SKILL.md files in repos", "research external skills", "find workflow patterns", "survey the skill landscape", "what skills exist out there", or wants to investigate public repositories for extractable processes, babysitter plugins, and reusable procedural insights. Searches GitHub for SKILL.md files, classifies repos by archetype, and maintains structured research under docs/reference-repos/.
>-
This skill should be used when the user asks to "babysit issues", "work on assigned issues", "check a5c-agent issues", "process babysitter issues", or wants to find and work on open GitHub issues assigned to a5c-agent in the babysitter repo.