/legacy

description: Legacy full orchestrator (triage, investigation wave, synthesis, DAG) — reached via /orchestrate --path full
argument-hint: "[milestone <slug> | #1 #2 #3 | next <N> | fast-lane | priority:P0] [--auto|--confirm]"
user-invocable: false
install: internal

<!-- SPDX-FileCopyrightText: Copyright (c) RapierCraft Studios --> <!-- SPDX-License-Identifier: AGPL-3.0-or-later -->

/orchestrate — Multi-Issue Parallel Orchestrator

**Input**: $ARGUMENTS

`--auto` and `--confirm` authorize the dispatch checkpoint; they are control flags, not part of the issue-set query. `--deep-plan` requests the full analysis path, and `--max-concurrent N` only tunes the dispatch cap.

This file is the slim dispatcher. Detailed phase content lives in `commands/orchestrate/`.

OpenCode Preflight

When `FORGE_RUNTIME=opencode` (or an OpenCode runtime marker is present), run the deterministic preflight at `$FORGE_HOME/bin/orchestrate-preflight.mjs` immediately, before reading `orchestrate/config.md`, this workflow, or any phase spec. The helper resolves the repository from `forge.yaml`, including a parent config when the target is a nested Git worktree:

node "$FORGE_HOME/bin/orchestrate-preflight.mjs" \
  --repo "$GH_REPO" \
  --args "$ARGUMENTS"

The preflight is a compact mechanical adapter for issue resolution, eligibility, explicit dependencies, scoped issue-body file overlap, database serialization, and the initial ready queue. If it returns a supported plan with `requiresDeepPlan: false` and `confirmed: true`, launch `dispatchNow` with native background `task` calls immediately. Without an explicit `--auto` or `--confirm` argument, present the compact plan and ask for one confirmation; after the user confirms, launch the plan's ready queue without re-reading the large phase files. Do not load the full Phase 3 or Phase 4 prose just to ask that question.

Continue through the phase files when the plan says `requiresDeepPlan`, the input is unsupported, preflight fails, or a task-result event requires recovery. This adapter never closes, deduplicates, or edits issues; the full shared workflow remains the authority for investigations, review-finding cascade handling, recovery, cleanup, and reporting.

For a supported compact OpenCode plan, stop after the fast-path dispatch. The phase execution order below is the fallback path for deep plans, unsupported inputs, preflight failures, and task-result recovery; do not read it merely to confirm or dispatch a compact plan.

Execution Order

Read and execute phases in sequence. Each phase file is self-contained. Resolve every path from the spec root defined in the Quick Reference below.

| Step | File | Description | |------|------|-------------| | 0 | `orchestrate/config.md` | Hard rules, config resolution, multi-repo support — READ FIRST | | 1 | `orchestrate/phase-1-resolve.md` | Resolve the issue set from input | | 2 | `orchestrate/phase-2-triage.md` | Investigation-first triage, Wave 0 | | 2.5 | `orchestrate/phase-2.5-synthesis.md` | Investigation synthesis and deconfliction | | 3 | `orchestrate/phase-3-dependency.md` | Dependency analysis, DAG construction, execution plan | | 4 | `orchestrate/phase-4-execution.md` | Streaming DAG execution, agent dispatch, stall detection | | 5 | `orchestrate/phase-5-cleanup.md` | Post-batch cleanup sweep and agent audit | | 6 | `orchestrate/phase-6-report.md` | Consolidated report and pipeline summary | | — | `orchestrate/safety.md` | Safety rules and examples (reference) |

Quick Reference

**Spec root (MANDATORY)**: read every file below from `${CLAUDE_PLUGIN_ROOT}` — the install root of the ForgeDock plugin that is running this command (Claude Code fills it in when it loads the spec). Only if that path does not start with `/` (not a Claude Code plugin session: install.sh, Codex, OpenCode) use `$FORGE_HOME` instead. Never read sub-files from `$FORGE_HOME` when the plugin root resolved: an exported `FORGE_HOME` can point at a different, older ForgeDock checkout, and mixing roots runs stale phase specs.

**Raw reads are not substituted (MANDATORY)**: Claude Code fills in the plugin root only in the spec it loads (this file), never in files you open with Read. The phase files contain the placeholder written as `$` immediately followed by `{CLAUDE_PLUGIN_ROOT}`. Before running any bash block taken from a phase file, replace every occurrence of that placeholder with `${CLAUDE_PLUGIN_ROOT}` (the resolved root shown here), exactly as Claude Code would have. Left unreplaced it is rejected as a non-absolute path and resolution falls back to `$FORGE_HOME`, which may be stale.

Read: ${CLAUDE_PLUGIN_ROOT}/commands/orchestrate/config.md       # ALWAYS READ FIRST
Read: ${CLAUDE_PLUGIN_ROOT}/commands/orchestrate/phase-1-resolve.md
Read: ${CLAUDE_PLUGIN_ROOT}/commands/orchestrate/phase-2-triage.md
Read: ${CLAUDE_PLUGIN_ROOT}/commands/orchestrate/phase-2.5-synthesis.md
Read: ${CLAUDE_PLUGIN_ROOT}/commands/orchestrate/phase-3-dependency.md
Read: ${CLAUDE_PLUGIN_ROOT}/commands/orchestrate/phase-4-execution.md
Read: ${CLAUDE_PLUGIN_ROOT}/commands/orchestrate/phase-5-cleanup.md
Read: ${CLAUDE_PLUGIN_ROOT}/commands/orchestrate/phase-6-report.md

The orchestrator reads only the phase file(s) relevant to the current step rather than loading the full 2300-line monolith upfront.