Software Engineering Collective

Tools / 04 · SI · Planning plugin

Ultrathink

Status: Open source · v0.3.0

Ultrathink is an open-source planning plugin for SI (Super Intelligence) coding agents, published as claude-ultrathink, that rewrites each prompt into an XML spec with a dependency graph, builds a graph of thought with parallel execution waves and asks clarifying questions before the agent writes code. Built by Spectrum Web Co in Sydney.

Ultrathink gives SI coding agents a plan to work from. Prompts become XML specs, specs become a graph of thought with parallel waves, and the clarifying questions are asked up front. An optional Ship flow takes the result through to a reviewed, merged pull request, with tasks tracked in Linear and Notion.

View the repo on GitHubTalk to us about agentic delivery

About

What is Ultrathink?

Ultrathink is the planning layer in KanbanOS, released as an open-source plugin under AGPL-3.0-or-later. It sits in front of the coding agent you already use, including Claude Code, Grok Build, Hermes Agent, Muse Code and Omp, and makes sure the work is understood before it is started.

  • Prompt to XML spec and dependency graph
  • Graph-of-thought parallel execution waves
  • Ship flow: PR, Greptile review and merge

01 — Plan

Every prompt becomes a spec.

Hooks intercept your prompt before the coding agent acts on it and rewrite it into an XML spec with a dependency graph: what has to be built, in what order, and what depends on what. Your agent receives a structured brief, not a one-line instruction.

  • Hook-based interception
  • XML specs
  • Dependency graphs

02 — Ask

Questions first.

Clarifying questions are drafted and put to you before work starts, so ambiguity is settled once instead of rediscovered halfway through a run and paid for in rework.

03 — Waves

A graph of thought, run in parallel.

The spec is expanded into a graph of thought organised into parallel execution waves. Tasks with no dependency on each other share a wave and can run in parallel, while tasks that depend on earlier work fall into later waves. The agent works through a plan with a visible shape instead of improvising one step at a time.

  • Graph of thought
  • Parallel execution waves
  • Dependencies resolved before work starts

04 — Ship

From plan to merged PR.

The optional Ship flow automates pull request creation, runs a Greptile code review and handles the merge. Linear and Notion integrations keep tasks in step with the plan, so the tracker reflects what the agent is actually doing.

Who it’s for

For anyone who has watched an agent guess.

Ultrathink is for developers and engineering teams who want SI coding agents to plan, ask and then execute, with the plan visible in the tools the team already uses.

  • Claude Code and Grok Build users
  • Teams tracking work in Linear or Notion
  • Leads who want pull requests reviewed before merge
  • Anyone tired of rework from vague prompts

FAQ

Ultrathink, answered.

01

How does Ultrathink plan prompts before coding starts?

Ultrathink intercepts your prompt through the host agent’s hooks before the coding agent acts on it. It rewrites the request into an XML spec with a dependency graph, expands that spec into a graph of thought organised into parallel execution waves, and drafts clarifying questions about anything ambiguous. The resulting plan is handed to your agent, so Claude Code or another host starts from a structured brief instead of a one-line instruction. Each planned prompt makes 8 to 11 headless model calls through the planning engine you configure.

02

Which coding agents does Ultrathink support?

Ultrathink supports five host agents: Claude Code, Grok Build, Hermes Agent, Muse Code and Omp. Planning runs through a supported planning engine you configure, such as the Claude CLI or Grok, and each planned prompt makes 8 to 11 headless model calls through that engine. Version 0.3.0, the first public release, is tested on Linux and macOS. Because the plugin is linked into each host’s plugin directory, one installation pattern covers every supported agent your team uses. Inside KanbanOS, Ultrathink is the planning layer.

03

How do I install and configure Ultrathink?

Install Ultrathink by cloning the claude-ultrathink repository from GitHub and linking it into each host agent’s plugin directory. You need Bun 1.2 or newer and a supported planning engine, such as the Claude CLI or Grok. Configuration lives in JSON files in ~/.config/ultrathink/, so the setup is plain text you can version and reproduce across machines. When a prompt does not need planning, skip it with the /ultrathink-quick command or a raw: prefix, and the message goes straight through to your agent unchanged.

04

What does Ultrathink cost, and how is it licensed?

Ultrathink is free software licensed under AGPL-3.0-or-later, so there is no licence fee for the plugin itself. The running cost is model usage: each planned prompt makes 8 to 11 headless model calls through your own configured planning engine. Budget for that on every planned prompt, and use /ultrathink-quick or the raw: prefix for trivial requests that do not need a plan. If you modify Ultrathink and offer it to others over a network, review the AGPL’s source-availability terms first.

05

How does Ultrathink connect to Linear, Notion and PR review?

Ultrathink can optionally sync planned tasks to Linear and Notion, so the plan your agent works from is visible in the trackers your team already uses. Its Ship flow then carries the work past the code: it automates pull request creation, runs a Greptile code review and handles the merge. Inside KanbanOS, Ultrathink is the planning layer, where one Graph ID follows each request across the board, Linear and Notion. Teams that do not need tracking or the Ship flow can leave both switched off and use Ultrathink purely for planning.