The built-in flows.

01Planner — idea in, backlog out

Planner turns a raw idea into a reviewed, ready-to-execute backlog. You describe what you want; the flow gathers context from your repo, optionally researches, writes an idea spec, and decomposes it into epics and tasks — pausing for your sign-off at each gate.

• Each gate offers real choices — approve, revise, or reject the spec; approve or revise the plan.
• Large ideas get an epic layer; small ones decompose straight to tasks.
• On approval the originating idea retires from the board — its tasks carry the work forward.

02Sprint — execute the ready work

Sprint takes a batch of ready tasks and executes them inside the session’s shared worktree. Independent tasks fan out to parallel subagents in dependency-aware waves — up to five at once, with tasks that touch the same files automatically serialized.

• Every task renders as a lane — a live progress row that ends running, integrated, failed, or blocked.
• Each integrated task lands as its own git commit in the worktree.
• A failed lane never blocks the others; the sprint closes with a full verification pass and a review summary, and you decide what merges.

03Ship — Planner ⊕ Sprint, one run

Ship runs the whole arc in a single session: research the idea, lock the spec, decompose it, then materialize a sprint over the approved tasks and execute every one to integration. The single Approve plan gate doubles as the pre-execution gate — you approve the plan and pick which tasks run now.

• Caps at 15 tasks per run on the SDK runtime (10 on interactive PTY).
• Ends at Approve sprint, then rests awaiting your review — nothing merges itself.

04Compound — the learning loop

Compound mines your recently merged runs for durable learnings and folds the approved ones back into the system — as clean-up tasks, review-queue findings, or proposed edits to your project docs. Doc edits are always human-gated; the flow never rewrites your conventions on its own.

• Unseeded: launch it cold and it digs through recent merges, drafts learnings, and brings them to an approval gate — approve all, pick a subset, or reject.
• Seeded: launch it from the Insights triage tray with hand-picked findings and it skips the gate, acting on exactly your selection and resolving each finding as fixed, triaged, or promoted.

05Custom flows & agents

The Workflows view is a cross-project gallery of every flow and agent. The built-ins are starting points, not fixtures — open any flow in the editor to reorder, add, or remove steps, or build a new flow from scratch.

• The agent editor lets you tune each agent’s prompt and behavior.
• Each agent can pin its own model — Fable 5, Opus 4.8, Sonnet 5, or Haiku 4.5 — or inherit the run’s model. See per-agent pins.
• Per-agent MCP servers and plugins are configurable the same way.