Claude-skill-registry complex-orchestrator

Orchestrates multi-file tasks by delegating to parallel sub-agents. Use when a task spans multiple files or components and can benefit from parallel execution to save context and time.

install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/complex-orchestrator" ~/.claude/skills/majiayu000-claude-skill-registry-complex-orchestrator && rm -rf "$T"
manifest: skills/data/complex-orchestrator/SKILL.md
source content

Parallel Task Orchestrator

Distribute multi-file work across parallel sub-agents to save context and time.

When to Use

Task spans multiple files?
    │
    ├─ Independent? ──────► Full Parallel
    ├─ Some dependencies? ─► Staged Parallel (waves)
    └─ Tightly coupled? ──► Sequential or single agent

4-Step Workflow

1. Decompose

Break into file-scoped units. Identify dependencies.

2. Choose Strategy

  • Full Parallel: All units independent
  • Staged Parallel: Wave 1 (dependencies) → Wave 2 (consumers)
  • Fan-out/Fan-in: Setup → parallel work → integration

3. Delegate in Parallel

Launch multiple Tasks in single message:

Task({ subagent_type: "general-purpose", description: "Edit file A", prompt: "..." })
Task({ subagent_type: "general-purpose", description: "Edit file B", prompt: "..." })

4. Integrate

  • Verify each succeeded
  • Check for conflicts
  • Run integration tests

Sub-agent Prompt Structure

## Scope
File: [path] | Task: [what to do in THIS file only]

## Context
Pattern: [consistent approach across all units]

## Constraints
- Only modify [path]
- Follow existing style

Agent Selection

Sub-taskAgent
Simple edit
general-purpose
Exploration needed
Explore
general-purpose
Complex logic
advanced-general-purpose

For detailed examples and troubleshooting, see

examples.md