Skip to content
Skills Library
Programming · Automation

forge-orchestrate

/forge-orchestrate

Use when an approved plan contains multiple bounded units that need dependency ordering, isolated worktrees, or parallel execution. Use forge-build for one work order and forge when the plan is not yet approved. Do not use for trivial or single-system work where orchestration overhead exceeds the task.

Repository
forge ↗
Licence
MIT
Last repository change
28.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 28.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when an approved plan contains multiple bounded units that need dependency ordering, isolated worktrees, or parallel execution. Use forge-build for one work order and forge when the plan is not yet approved. Do not use for trivial or single-system work where orchestration overhead exceeds the task.

Original author description

Use when an approved plan contains multiple bounded units that need dependency ordering, isolated worktrees, or parallel execution. Use forge-build for one work order and forge when the plan is not yet approved. Do not use for trivial or single-system work where orchestration overhead exceeds the task.

How it works

  1. Unique to this skill
  2. Execution profile
  3. Canonical references
  4. What NOT to do
Original SKILL.md headings · 50 lines, 332 words
SKILL.md preview
---
name: forge-orchestrate
description: Use when an approved plan contains multiple bounded units that need dependency ordering, isolated worktrees, or parallel execution. Use forge-build for one work order and forge when the plan is not yet approved. Do not use for trivial or single-system work where orchestration overhead exceeds the task.
---

# FORGE-ORCHESTRATE — Split a Frozen Spec Across Models

Act 4 standalone: decompose an APPROVED spec into units, run independent ones
concurrently in isolated worktrees, integrate in dependency order. For a single-track
build use `/forge-build`; to plan first use `/forge`.

## Unique to this skill

0. **Route first.** Read [`../forge/SKILL.md`](../forge/SKILL.md), resolve the active
   profile, and use [`../forge/ENGINE.md`](../forge/ENGINE.md) for preflight before any
   launch. The steps below do not override that profile.
1. **Preconditions.** Plan APPROVED; clean base tree. If the repo has a protocol
   (`AGENTS.md` / `.ai/COLLAB_PROTOCOL.md`), follow its branch/worktree naming.
2. **Decompose** into the smallest units that each have a clear done-condition, a
   **proof** (declared `targeted` or `broad`), and a knowable file set. Classify each
   pair independent (disjoint files → may run in parallel) or dependent (shared files or
   ordering → serial). When unsure, serialize.
3. **Worktrees.** One isolated worktree per concurrent unit; **one writing agent per
   tree**. To widen a unit's file set mid-flight, use one **guarded re-admission**
   (`--admission-action expand`) — same lane, no restart, still rejects overlap.
4. **Execute** independent units together within the guard's caps.
5. **Integrate** passing units in dependency order, then run the profile's validation.
   **The driver merges and commits — never the executor.**

Tunables: `SPEC_FILE=PLAN.md` · `MAX_FIX_ROUNDS=2` · `LOG_FILE=PLAN-REVIEW-LOG.md`.
Concurrency is the guard's, not this file's: three lanes total, one HEAVY lease.

## Execution profile

Before product execution, read [`../forge/SKILL.md`](../forge/SKILL.md) and the one
selected file in [`../forge/profiles/`](../forge/profiles/). Those sources alone own
cadence, review, proof, routing, and integration. Do not reconstruct or add ceremony
here. Every lane still passes [`../forge/dispatch-guard.sh`](../forge/dispatch-guard.sh).

## Canonical references

[`../forge/ROUTING-POLICY.md`](../forge/ROUTING-POLICY.md) (routing) ·
[`../forge/profiles/`](../forge/profiles/) (cadence) ·
[`../forge/ENGINE.md`](../forge/ENGINE.md) (engine, templates, admission) ·
[`../forge/references/`](../forge/references/) (detail, on demand)

## What NOT to do

- Don't hand-wave concurrency — the guard decides, per lane.
- Don't restate Act-3/4 cadence here; the profile owns it.
- Don't wait at Gate 2 under `sprint` — apply the overlay/default and record one line.
- Don't call a same-model subagent review cross-model (and under `sprint` there is no
  per-unit review at all).

Versions

RepositoryScoreLicence
This page · 3orionkings/forge90MIT
nixlim/forge-plugin95MIT
3orionkings/forge90MIT

Database snapshot: 13.11.2026 · package version d169192323bc (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90forge-build
    Use when the user supplies an approved or frozen work order for one executor, including a bounded refactor, migration, bug fix with a known repro, or test-writing task. Use forge-orchestrate for multiple parallel units and forge for unresolved design. Do not use for tiny edits,…
  • 90forge
    Use when the user asks to forge, plan and build, or cross-model stress-test a non-trivial change before guarded execution. Use forge-review for plan review only, forge-build for one frozen work order, forge-orchestrate for a multi-unit build, and forge-recovery only for a…
  • 100best-of-n
    Implement a task N ways in parallel and pick the best. Spawns multiple subagents in isolated worktrees, evaluates all candidates, and applies the winner. Use when asked to "best of n", "try multiple approaches", "parallel implementations", "/best-of-n", or "/bon".
  • 100forge
    Spec-driven autonomous development workflow. When the user wants to plan a non-trivial change, build it autonomously, or run a skeptical review of completed work, use the /forge:* commands. /forge:contract writes a rich spec through code exploration, library research, and…
  • 90sy-work
    Build only the approved slice while preserving scope, unrelated worktree changes, and validation evidence. Use when an approved execution plan or explicit bounded task is ready for implementation.
  • 91forge
    Run Forge, which takes a story from approval to a merged pull request. Use when the human asks what to do next, wants to plan a story, start a task or fix, build, close, save a spec or decision, add to the roadmap, check the setup, or see the board.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.