Ordewell

Turn one goal into an ordered plan of coding-agent tasks — each with its own runner, model and mode — then execute and verify it.

What this is:

Give one goal, get back an ordered plan of coding-agent tasks — and you control every part of it before anything runs.

• The plan is a file you rewrite before anything runs. Every task carries its runner, model, thinking effort and mode. Change any of them, add and remove tasks, rewire dependencies — completed work survives, and nothing runs until you say go.
• One runner and model per task, all visible at once. A security refactor and a README update don't deserve the same model. The planner assigns across the whole plan and shows you every assignment first (why a separate planner?).
• A task is done when its completion marker appears in the runner's output — and not before. Exit code is kept as diagnostic evidence. No model grades its own work, and a task that ends without its marker fails loudly instead of passing quietly.
• The planner is read-only and talks to you. It researches the repo, 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).
• 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.