Skip to content
Sign in

workflow

Multi-agent work on the kanban board, one workflow run per wave: the ticket strategy of iii/deepwork (a run ticket, subtask cards, bounded rounds, independent verification) with every phase as a workflow node, each one with its own profile and model, retried by the run's check loop. Code goals get one worktree per ticket, one tests-and-check run per integrated wave and a kept branch. Installs beside iii/deepwork.

Install0.1.3

# With the iii engine running

iii trigger directory::download-kit kit=iii/workflow@0.1.3
6Installs
6Last 7 days
0Today
30 days

Exact versions are immutable. Every profile and skill is stored by its SHA-256, so updates show exactly what changed.

Installing the kit adds each worker to your compose graph at the newest version its range allows. Ranges are resolved again on every install and update.

  • Worker
    Lodash-style value transforms (fp::get/pick/take/…) and fp::pipe — worker-side pipelines that move big values function→function without routing them through the model.
    Range>=0.3.0Resolves tov0.3.2
    Functions used2
    • fp::get
    • fp::pipe
  • Worker
    Thin durable turn loop that wires session-manager, context-manager, and llm-router into an agent loop; spawns sub-agents as child sessions.
    Range^1.9.9Resolves tov1.9.14
    Functions used5
    • harness::ask
    • harness::metrics
    • harness::observe
    • harness::observers::list
    • harness::unobserve
  • Worker
    Unix shell + filesystem worker — exec with denylist/timeout/output caps and background jobs; fs::ls|stat|mkdir|rm|chmod|mv|grep|sed|read|write with host jail, denylist, size caps, and sandbox-target forwarding
    Range>=0.13.0Resolves tov0.13.7
    Functions used8
    • coder::create-file
    • coder::read-file
    • coder::tree
    • coder::update-file
    • shell::exec
    • shell::exec_bg
    • shell::kill
    • shell::status
  • Worker
    Engine introspection, workers registry proxy, filesystem-backed skills, system prompts, and agent profiles, kit install and update with reviewed plans, plus function search ranked by the judge worker (falling back to local hybrid/lexical) with a conditional pre-generate hint.
    Range>=1.3.0Resolves tov1.3.8
    Functions used1
    • directory::agents::get
  • Worker
    File-backed kanban board — tickets, threaded comments, agent assignment, the kanban::on-change and kanban::on-comment event functions, and an injectable console board with agent profiles for planning and review.
    Range^0.2.0Resolves tov0.2.4
    Functions used7
    • kanban::comment::create
    • kanban::config::info
    • kanban::project::create
    • kanban::ticket::create
    • kanban::ticket::get
    • kanban::ticket::list
    • kanban::ticket::update
  • Worker
    Distributed key-value state management — registers the `state::*` functions and `state::on-changed`, a private function observers watch for every committed change.
    Range>=0.23.0Resolves tov0.23.3
    Functions used2
    • state::get
    • state::set
  • Worker
    Deterministic, crash-resumable multi-agent workflow orchestrator over harness turns.
    Range>=0.3.0Resolves tov0.3.5
    Functions used5
    • workflow-result::submit
    • workflow::node-result
    • workflow::start
    • workflow::status
    • workflow::stop
Unknown functions
router::models::list are preloaded by a profile but not served by any declared worker. They only work if something else in your project registers them.

Search the registry

Find workers, kits and executables, or jump to a page.