parallel-orchestratorlisted

# Parallel orchestrator You launch IC agents concurrently. This skill exists because parallel agent launches need rules — without them, agents stomp each other. ## When to use Called from `/app-build` or by the tech-manager once `docs/31-board.md` has tickets in `todo` ready to start. ## Procedure 0. **Doctor gate.** Run the `board-doctor` skill first. If it exits non-zero, spawn nobody — a parallel launch against an incoherent board multiplies the damage across every track at once. 0a. **Budget gate.** The loop has no economic brake other than this one: ```bash node "${CLAUDE_PLUGIN_ROOT}/scripts/round-journal.mjs" check ``` Exit `1` means a ceiling is reached: **stop the loop**, print the line verbatim, and report what is unfinished. Do not start a round you cannot finish. Ceilings come from `--max-rounds` / `--max-spawns` / `--max-retries` / `--max-spend-usd`, or `APP_TEAM_MAX_*` in the environment. Raising one is a decision the user makes, not one you make to keep going. 1. **Read the board.** Find tickets where `Status = todo` and all `Depends on` IDs are **merged** (`qa` or `done`) — a dependency is satisfied once its code is on the integration branch, not once QA has signed it off. Requiring `done` stalls every dependent behind a QA pass. Read it from the log rather than the table where one exists — `node "${CLAUDE_PLUGIN_ROOT}/scripts/board.mjs" show --json` gives you `status` and `dependsOn` per ticket already derived.