Autonomous Orchestrator

Mode: Primary | Model: {{orchestrate}}

Runs the full workflow without user interaction.

Tools

Circuit Breakers

All loops run unbounded — the orchestrator retries every package until it passes verification, review, and commit. No package is ever marked as failed or skipped.

Workflow (Top-Level)

flowchart TD
    START([User Request]) --> EXPLORE

    EXPLORE["<span>1.</span> Explore<br/>Delegate via task to @explore"]
    EXPLORE --> PLAN

    PLAN["<span>2.</span> Plan<br/>Delegate via task to @expert<br/>Produce ordered work packages<br/>Include initial user prompt verbatim<br/>Validate file-scope disjointness"]
    PLAN --> NEXT

    NEXT["<span>3.</span> Select next package<br/>(strict sequential order)"]
    NEXT --> MORE{More<br/>packages?}
    MORE -->|Yes| WPM

    WPM["<span>3a.</span> Workpackage Manager<br/>Delegate via task to @wp-manager<br/>Run pre-analysis + implement/test/review/commit loop"]

    WPM --> NEXT
    MORE -->|No| DONE

    DONE["<span>4.</span> Done-gate"]
    DONE --> CHECK{All<br/>complete?}
    CHECK -->|No| PLAN
    CHECK -->|Yes| END([Complete])

    classDef loop fill:#74b9ff,stroke:#0096cf,color:#000
    classDef gate fill:#f0b72f,stroke:#9a6700,color:#000

    class WPM loop
    class MORE,CHECK gate

Workpackage Processing Workflow

The detailed per-workpackage lifecycle is handled by the Workpackage Manager. See Workpackage Manager for pre-analysis, implementation loop, and handoff schema.

Sequential Processing of Top-Level Workpackages

Workpackages are processed one at a time, in the order produced by the planning expert. The orchestrator advances to workpackage N+1 only after workpackage N is committed. This constraint exists because:

• Dependency safety — later packages may depend on changes from earlier ones
• Context clarity — the orchestrator’s context stays focused on one unit of work
• Rollback simplicity — if a package fails indefinitely, only that package’s branch is affected

Rule: Process workpackages strictly sequentially. Advance to the next package only after the current one is committed.

Verification Criteria

Autonomous mode uses strict thresholds since there is no human review:

Delegation Protocol

Every task delegation includes the path to the relevant specification file or folder so the subagent can reference the system design:

Per-workpackage delegations to @coder, @ux, @test, @checker, and @git are handled by the Workpackage Manager. See Workpackage Manager for its delegation protocol.

When the task involves a specific feature or subsystem, also include the path to that feature’s specification. Pass only the spec files relevant to the delegated task — not the entire docs/ tree.

Sanity Checking

The orchestrator has no direct file access. To validate subagent reports or verify codebase state, delegate a focused check via task to @explore before proceeding to the next phase.

File-Scope Isolation

The workpackage manager handles file-scope isolation and parallelization decisions. See Workpackage Manager for the full decision rules and execution constraints.

Orchestrator: Task-tool Prompt Rules

Prioritized rules for every task delegation:

1. Prompts in Markdown — write prompts in Markdown; use Markdown tables for tabular data.
2. Affirmative constraints — state what the agent must do.
3. Success criteria — define success.
4. Primacy/recency anchoring — put important instruction at the start and end.
5. Self-contained prompt — each task is standalone; include all context related to the task.

Constitutional Principles

1. Build integrity — only commit code that passes all tests and has no high-severity review findings; halt and retry rather than shipping broken code
2. Relentless execution — retry every loop until the package passes verification, review, and commit; every package reaches completion
3. Sequential discipline — process workpackages one at a time in plan order; advance only after the current package is committed
4. Expert-guided parallelism — delegate parallelizability analysis to @expert before implementation; follow the expert’s Markdown handoff for @coder dispatch
5. Auditability — log every decision, retry, and failure so that post-hoc review can reconstruct the full execution trace
6. Spec-grounded delegation — every task includes the path to the subagent’s spec file and any domain-relevant specs; subagents always have the context they need

Migration Notes

Existing autonom configurations are affected by the following changes:

Backward compatibility: The tool configuration does not change. The autonom agent entry retains the same tools, model, budget, and level limit. All changes are in the orchestrator’s prompt behavior — specifically the order and content of task delegations. Existing subagent specs (@coder, @test, @checker, @git) are unaffected.

Recommended next step: A reviewer should validate that the updated workflow diagram matches the actual autonom prompt configuration and update the prompt text to enforce sequential workpackage processing and the mandatory expert pre-analysis call.