forge-orchestratelisted

OpenCode-only. Drive the full 12-stage Forge pipeline end-to-end by adopting the Orchestrator persona — runs each stage's own skill in turn, checks its gate, and explicitly advances and verifies pipeline/state.md before moving on. Use when the user runs /forge:orchestrate, says "orchestrate the pipeline", "run the whole pipeline", "drive this end-to-end", "take this from SRS to release", or "act as the pipeline orchestrator". Exists because OpenCode's Stop hook has no transcript-based auto-advance signal — state.md would otherwise stop tracking per-stage progress. For self-healing / background-dispatch / context-checkpointed runs, prefer /forge:autopilot instead (see Relationship note below).
tonmoy007/forge-plugins · ★ 1 · AI & Automation · score 72

Install: claude install-skill tonmoy007/forge-plugins

# /forge:orchestrate — full-pipeline orchestration (OpenCode) `/forge:orchestrate` is the OpenCode-native answer to "run the pipeline for me." It adopts the Orchestrator persona (`agents/orchestrator.md`) and walks the pipeline stage-by-stage, reusing each stage's own `/forge:*` skill — never reimplementing stage logic — while owning one thing every stage's skill does *not* reliably own under OpenCode: verifying `pipeline/state.md` actually advanced. ## When to Use - `/forge:orchestrate` (defaults to running through to stage 12, or the current cycle's exit stage). - `/forge:orchestrate to stage N` — run up to and including stage N. - `/forge:orchestrate iteration` / `hotfix` / `tech-debt` — run one of the named cycles from `references/stage-order.md`'s `cycles` table (entry → exit). - The user wants several stages driven without issuing each `/forge:*` command by hand, and wants a persona explicitly accountable for the pipeline bookkeeping. ## When NOT to Use - A single stage → just run that stage's own command (e.g. `/forge:build`). - The user wants self-heal on gate failure, background dispatch, or context-window checkpointing → that's `/forge:autopilot`, which already implements all three (see Relationship note below); don't duplicate that machinery here. - The user wants to override a known blocker → `/forge:force-advance`, not this. ## Relationship to `/forge:autopilot` Both skills drive multiple stages. Use this table to route: | Need | Use | |---|---|