GoKawiilTurn one goal into an ordered plan of coding-agent tasks — each with its own runner, model and mode — then execute and verify it.
Website · Docs
What this is
A plan you can rewrite before a token is spent. The plan is a typed artifact, not an agent's internal state: every task carries a runner, model, thinking effort and mode, and you can change any of them, add and remove tasks, and rewire dependencies — without losing completed work or round-tripping the AI.
The plan is a typed artifact, not an agent's internal state: every task carries a runner, model, thinking effort and mode, and you can change any of them, add and remove tasks, and rewire dependencies — without losing completed work or round-tripping the AI. The right model per task, chosen in the open. The planner makes one portfolio decision across the whole plan — a security refactor and a README update do not deserve the same model — and shows you every assignment before anything runs (why a separate planner?).
The planner makes one portfolio decision across the whole plan — a security refactor and a README update do not deserve the same model — and shows you every assignment before anything runs (why a separate planner?). Verdicts from evidence, not opinion. A task completes only when its unique completion marker appears in the runner's output; exit code is retained as diagnostic evidence. The model is never the tie-breaker. Stuck tasks can be advanced with Mark complete, and a task marked done by mistake goes back with Mark not done.
A task completes only when its unique completion marker appears in the runner's output; exit code is retained as diagnostic evidence. The model is never the tie-breaker. Stuck tasks can be advanced with Mark complete, and a task marked done by mistake goes back with Mark not done. A planner that talks back. Planning is one continuous chat: it researches your repo read-only, asks when your goal is vague, and its final message is the plan (ADR-0002). Reads run in parallel; anything reaching outside the workspace asks once; commands that would write are refused outright (ADR-0008).
Planning is one continuous chat: it researches your repo read-only, asks when your goal is vague, and its final message is the plan (ADR-0002). Reads run in parallel; anything reaching outside the workspace asks once; commands that would write are refused outright (ADR-0008). No extra API key required. Claude Code, Codex, or OpenCode can be the planner, strictly read-only, on the subscription you already hold for the runners (ADR-0009).
Claude Code, Codex, or OpenCode can be the planner, strictly read-only, on the subscription you already hold for the runners (ADR-0009). Multi-runner by design. Enable several and the planner assigns one per task. Claude Code, Codex and OpenCode ship built-in; anything else — Aider, your own CLI — is a plugin manifest, not a code change.
Quick Start
... continue reading