open/ktg-plugin-marketplace
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity Actions

feat(ultraplan-local)!: v2.4.0 — orchestrator agents as inline reference

Browse source 
Redefine research-orchestrator, planning-orchestrator, and
architect-orchestrator from "background executor" to "inline
reference documentation". The agent files remain as the canonical
workflow descriptions, but the /ultra* commands now execute the
phases directly in the main command context instead of spawning
these agents as sub-agents.

The /ultra* command markdowns are now the de-facto orchestrators.
Splitting work into a separate sub-agent was incompatible with the
harness's treatment of the Agent tool (not exposed to sub-agents).

BREAKING CHANGE: These agents are no longer invoked. Any external
integration that spawned them directly should now invoke the
corresponding /ultra* command instead.
This commit is contained in:
Kjell Tore Guttormsen 2026-04-19 21:24:45 +02:00
commit c8a6506384
3 changed files with 65 additions and 100 deletions
Download patch file Download diff file Expand all files Collapse all files

54
plugins/ultraplan-local/agents/planning-orchestrator.md
View file

@ -1,36 +1,14 @@
---
name: planning-orchestrator
description: |
Use this agent to run the full ultraplan planning pipeline (exploration, research,
synthesis, planning, adversarial review) as a background task. Receives a task
brief and produces a complete implementation plan.
<example>
Context: Ultraplan default mode transitions to background after brief is available
user: "/ultraplan-local --project .claude/projects/2026-04-18-websocket-notifications"
assistant: "Brief loaded. Launching planning-orchestrator in background."
<commentary>
Phase 3 of ultraplan spawns this agent with the brief file to run Phases 4-10 in background.
</commentary>
</example>
<example>
Context: User plans from a brief produced by /ultrabrief-local
user: "/ultraplan-local --brief .claude/projects/2026-04-18-jwt-auth/brief.md"
assistant: "Brief loaded. Launching planning-orchestrator in background."
<commentary>
Brief-driven mode spawns this agent immediately with the provided brief.
</commentary>
</example>
<example>
Context: User wants to re-run planning with an updated brief
user: "Re-plan with the updated brief"
assistant: "I'll launch the planning-orchestrator with the updated brief file."
<commentary>
Re-planning request triggers the orchestrator with the revised brief.
</commentary>
</example>
Inline reference (v2.4.0) — documents the planning workflow that
/ultraplan-local executes in main context. This file is NOT spawned as a
sub-agent anymore. The Claude Code harness does not expose the Agent tool
to sub-agents, so an orchestrator launched with run_in_background: true
cannot spawn the exploration swarm (architecture-mapper, task-finder,
plan-critic, etc.) and would degrade to single-context reasoning. The
/ultraplan-local command now orchestrates the phases below directly in the
main session.
model: opus
color: cyan
tools: ["Agent", "Read", "Glob", "Grep", "Write", "Edit", "Bash", "TaskCreate", "TaskUpdate"]
@ -45,11 +23,19 @@ tools: ["Agent", "Read", "Glob", "Grep", "Write", "Edit", "Bash", "TaskCreate",
Orchestrator Phase 5 = Command Phase 8 (Deep planning)
Orchestrator Phase 6 = Command Phase 9 (Adversarial review)
Orchestrator Phase 7 = Command Phase 10 (Completion)
This agent handles Phases 4–10 when mode = default (background). -->
As of v2.4.0, /ultraplan-local runs these phases inline in main context
instead of spawning this agent. Keep this file as the canonical
reference for what those phases do. -->
You are the ultraplan planning orchestrator. You receive a task brief and produce
a complete, adversarially-reviewed implementation plan. You run as a background
agent while the user continues other work.
This document is the canonical workflow description for the ultraplan
pipeline as of v2.4.0. The `/ultraplan-local` command reads it as reference
and executes the phases below **inline in the main command context**. It is
no longer spawned as a background sub-agent — that mode silently lost the
Agent tool and degraded the exploration swarm to single-context reasoning.
The role of the "orchestrator" now belongs to the command markdown itself:
the main Opus session launches exploration and review agents via the Agent
tool, collects their results, synthesizes the plan, and writes it to disk.
## Input