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.6

# With the iii engine running

iii trigger directory::download-kit kit=iii/workflow@0.1.6
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.

v0.1.5 → v0.1.6

Release notes · v0.1.6
  • A provider hiccup no longer drops a design, refute or check node. Every workflow-planner and workflow-verifier node (explore, design, refute, plan, check, batch check, baseline, critic and the review's refuters) is marked read_only. When its turn fails on a transient provider failure after the harness's own retries, the workflow worker waits a minute and continues it once in its own session, so the work it already did is kept and not paid again; the plan no longer runs on five of six inputs because one refuter hit a provider outage. Work, code and batch nodes change files or do the work itself, so a failure still fails them. The node keeps its timeout_ms, so a run's deadline timer is unchanged, and one that fails with less than 7 minutes of it left (at its deadline, say) still fails at once, since its continue would have no time to finish.
  • Requires workflow 0.3.4 (the read_only node key; an older worker refuses every run) and harness 1.9.13 (failure.retryable on harness::status).

Profiles

1 change
modifiedagents/workflow.md+5-4
@@ -99,14 +99,15 @@
9999 - passes `"idempotency_key":"<run>-<label>"` (labels below), so a retried start returns the same run;
100100 - has `"nodes"` as an object, never a JSON string, beside `"default_functions":{"allow":["*"],"deny":DL}`;
101101 - names its `"output"` explicitly, so the result's shape never depends on the graph;
102-- gives every node `"retries":0`, `"on_error":"continue"` (a failed node reads `null` and its siblings go on), `"timeout_ms"` = (its deadline + 2) × 60000, a `"label"` of at most 80 characters and a `"phase"`.
102+- gives every node `"retries":0`, `"on_error":"continue"` (a failed node reads `null` and its siblings go on), `"timeout_ms"` = (its deadline + 2) × 60000, a `"label"` of at most 80 characters and a `"phase"`;
103+- gives `"read_only":true` to every node whose profile is `workflow-planner` or `workflow-verifier`, and never to a `workflow-worker` or `workflow-impl` node: the worker continues a read-only node once, in its own session, after a transient provider failure.
103104
104-The request has these top-level keys: `idempotency_key`, `max_concurrency`, `default_functions`, `nodes` (node ids to nodes) and `output`. A node has exactly these keys: `task` (what the node does), `profile`, `model` (left out for a pinned tier), `schema`, `filesystem_root` (dev flow), `label`, `phase`, `timeout_ms`, `retries`, `on_error`, `reads` on a node that takes other nodes' results, and, on a check, `loop`; the review's refute node has `"fanout":"critic.new_items"` and no `reads`, so each copy receives its finding. A node without `reads` or `fanout` gets the run's `input`, which you never set: everything a node needs is in its `task`. `reads`, `fanout` and `output` name bare node ids, never `node:<id>`. A whole plain wave of one ticket, attempts=2, deadline_min=20, verify_deadline_min=40:
105+The request has these top-level keys: `idempotency_key`, `max_concurrency`, `default_functions`, `nodes` (node ids to nodes) and `output`. A node has exactly these keys: `task` (what the node does), `profile`, `model` (left out for a pinned tier), `schema`, `filesystem_root` (dev flow), `label`, `phase`, `timeout_ms`, `retries`, `on_error`, `read_only` on a planner or verifier node, `reads` on a node that takes other nodes' results, and, on a check, `loop`; the review's refute node has `"fanout":"critic.new_items"` and no `reads`, so each copy receives its finding. A node without `reads` or `fanout` gets the run's `input`, which you never set: everything a node needs is in its `task`. `reads`, `fanout` and `output` name bare node ids, never `node:<id>`. A whole plain wave of one ticket, attempts=2, deadline_min=20, verify_deadline_min=40:
105106 ```json
106107 {"idempotency_key":"wf-kan-7-a1b2c3-r1-w1","max_concurrency":4,"default_functions":{"allow":["*"],"deny":DL},
107108 "nodes":{
108109 "kan-12-work":{"profile":"workflow-worker","model":"<m>","schema":WORK,"task":"Mode: work. Ticket KAN-12, …","label":"KAN-12 · Summarize the API","phase":"work","timeout_ms":1320000,"retries":0,"on_error":"continue"},
109- "kan-12-check":{"profile":"workflow-verifier","model":"<m>","schema":VERDICT,"reads":"kan-12-work","task":"Mode: check. Ticket KAN-12, …","label":"verify:KAN-12","phase":"verify","timeout_ms":2520000,"retries":0,"on_error":"continue","loop":{"body":["kan-12-work"],"while":{"field":"verdict","equals":"fail"},"max_repeats":1}}},
110+ "kan-12-check":{"profile":"workflow-verifier","model":"<m>","schema":VERDICT,"reads":"kan-12-work","task":"Mode: check. Ticket KAN-12, …","label":"verify:KAN-12","phase":"verify","timeout_ms":2520000,"retries":0,"on_error":"continue","read_only":true,"loop":{"body":["kan-12-work"],"while":{"field":"verdict","equals":"fail"},"max_repeats":1}}},
110111 "output":["kan-12-check","kan-12-work"]}
111112 ```
112113 A refused start lists every shape problem at once, but only the first rule it breaks (labels, timeouts, loops, fanout, folders): fix that rule on every node, check the rest of the request against the rules above, and send it again.
@@ -209,7 +210,7 @@
209210 When the goal is itself a ticket key, that ticket is R: update it to `in_progress` with `"add_labels":["wf:run"]` and append the sections above, under a `---` rule, to its description.
210211 5. Preflight the pointer: `state::set` its `batch` key to `{"item":"batch","keys":[]}`. If refused: comment the reason on R, update R to `backlog` with `"add_labels":["blocked"]`, stop and name the function to allow.
211212 6. **Worktree** (dev flow), cwd = root: `shell::exec {"command":"git","args":["worktree","add","<W>","-b","<branch>","<base>"]}`, then `shell::exec {"command":"git","args":["check-ignore","-q",".worktrees/"]}`; when check-ignore exits non-zero, `shell::exec {"command":"sh","args":["-c","echo .worktrees/ >> \"$(git rev-parse --git-common-dir)/info/exclude\""]}`. A failed add: comment the error on R and finish with `blocked: worktree` (no git command, no Finish card). Then `shell::exec {"command":"df","args":["-Pk","<W>"]}`: under min_free_gb × 1048576 KB free (fourth column, second line), comment `blocked: disk` on R and finish.
212-7. **Design run** (Design = `run`, else go to Step A.8; label `plan`; plain flow: right after Step A.5). One run that explores before anything is planned, `"max_concurrency":8`, every node with `"retries":0` and `"on_error":"continue"`, and in the dev flow `"filesystem_root":"<W>"` on each:
213+7. **Design run** (Design = `run`, else go to Step A.8; label `plan`; plain flow: right after Step A.5). One run that explores before anything is planned, `"max_concurrency":8`, every node with `"retries":0`, `"on_error":"continue"` and `"read_only":true`, and in the dev flow `"filesystem_root":"<W>"` on each:
213214 - dev flow: the `baseline` node of Step A.10, so the checks at base run beside the exploration;
214215 - three explore nodes, phase `explore`: `"explore-<angle>":{"profile":"workflow-planner","model":"<work model>","schema":WORK,"task":"Mode: explore. Angle: <angle>. Run ticket <R>: read its goal with kanban::ticket::get.\n<dev: Worktree: <W>.\n>Deadline: <deadline_min> min.\nFunctions: <Functions>","label":"explore:<angle>","phase":"explore","timeout_ms":…}`, angles `code` (plain flow: `sources`), `constraints` and `options`;
215216 - three design nodes, phase `design`: `"design-<stance>":{"profile":"workflow-planner","model":"<plan model>","schema":WORK,"reads":["explore-<angle>",…],"task":"Mode: design. Stance: <stance>. Run ticket <R>. Flow: <dev or plain>. The input holds the explore findings.\nDeadline: <deadline_min> min.\nFunctions: <Functions>","label":"design:<stance>","phase":"design",…}`, stances `minimal`, `robust` and `fit`;

Workers

2 changes

Skills

0 changes

No skill changes.

Capabilities

0 changes

This update grants no new capabilities.

Search the registry

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