skill-parallel-orchestration

# Parallel Orchestration Skill **Purpose**: vendor-agnostic protocol for the Orchestrator Role to decompose large tasks into independent units and execute them via parallel sub-agent spawning. Specific tool names, directory layouts, and invocation syntax are delegated to per-vendor reference files in `references/`. --- ## 1. Load the right reference (mandatory step — Read tool, now) Before applying any protocol below, **use the `Read` tool to load the matching reference file now**. Do not proceed to §2 with only this SKILL.md in context — the reference supplies the concrete tool names and invocation syntax that the universal concepts below need to become executable. ### 1.1 Detection Walk upward from the current working directory toward the filesystem root (or stop at a `.git` boundary if that's closer) and check for vendor markers: | Runtime indicator (first match wins) | `Read` | Status | |---|---|---| | `CLAUDE.md` + `.claude/agents/` present | [`references/claude-code.md`](references/claude-code.md) | Reference implementation (complete, smoke-tested) | | `.codex/agents/` directory present | [`references/codex-cli.md`](references/codex-cli.md) | **Scaffold** — primitives documented from primary docs (parallel ✅ confirmed); not yet e2e-validated | | `GEMINI.md` present, no `.claude/agents/` | [`references/gemini-cli.md`](references/gemini-cli.md) | **Scaffold** — subagent format documented; ⚠️ Layer-A (parallel) unconfirmed in primary docs | | `.cursor/` directory pr...