17 17 | `return` | no | string (one selector token) | Selects the workflow's final value from phase results. |
19 19 `args` may also declare `params`: an ordered list of input names. A bare
20 -`/ultra <name> tokA tokB` line then maps `tokA`, `tokB` onto them positionally
21 -(extra tokens ignored), exposed as `{args.NAME}`. Without `params`, pass inputs
22 -as a trailing JSON object — `/ultra <name> {"k": "v"}`. A missing `{args.NAME}`
23 -renders to the empty string.
20 +`/ultra <name> tokA tokB` line maps tokens onto them positionally; the last declared parameter absorbs all remaining tokens so it can carry free text. Values are exposed as `{args.NAME}`. Without `params`, pass inputs as a trailing JSON object — `/ultra <name> {"k": "v"}`. A missing `{args.NAME}` renders to the empty string.
58 55 | `tools` | no | string[] | Tool allowlist. Omit for a tool-less completion (pure reasoning). |
59 56 | `model` | no | string | `provider/id` override, or configured tier `small`/`medium`/`big`; defaults to the session model. |
60 57 | `thinkingLevel` | no | off…xhigh | Reasoning budget for this step. |
61 -| `schema` | no | string
\| JSON Schema | A `schemas` name, or an inline schema. Forces structured output. |
58 +| `schema` | no | string
\| JSON Schema | A `schemas` name, or an inline schema that validates structured output. |
63 -A string `schema` is a **name reference** and must resolve in the spec's
64 -`schemas` map, or validation fails.
60 +Every step returns a JSON object through completion parsing or the terminating `structured_output` tool.
61 +Without `schema`, any JSON object is accepted.
62 +A `schema` validates that object and is required when downstream phases depend on a stable shape.
63 +A string `schema` is a **name reference** and must resolve in the spec's `schemas` map, or validation fails.
66 65 Configured model tiers live in Pi settings under `ultra.modelTiers`.
67 66 If a step sets `model` to `small`, `medium`, or `big`, ultra resolves it through that map; an unset tier falls back to the session model.
138 137 "prompt": "Read the file at {item} and return JSON with two string fields: path (the file path you were given) and summary (one sentence). Do not modify anything.",
139 138 "tools": ["read"],
140 + "thinkingLevel": "low",
141 142 "type": "object",
155 -## Worked example — two phases with a join key (the shipped `review`)
156 +## Worked example — two phases with a join key
157 158 Fan out a review across dimensions, then fan out verification over the flattened
158 159 findings. `Findings.file` → `Verdict.file` is the join key; `return` filters to
207 208 "prompt": "Review the diff for {item} issues. Inspect it with `git diff {args.base}` (no base ref → the working tree; a base ref → everything since that ref), plus read/grep as needed; do not modify any files. Return JSON matching the Findings schema, and set each finding's file to the path it concerns.",
208 209 "tools": ["read", "bash", "grep", "find", "ls"],
211 + "thinkingLevel": "medium",
209 212 "schema": "Findings"
215 218 "over": "{review.results[].findings[]}",
217 220 "prompt": "Adversarially try to refute this finding. Default to real=false if uncertain. Echo the finding's file verbatim in your verdict's file field so the verdict ties back to its finding. Finding: {item}",
222 + "thinkingLevel": "high",
218 223 "schema": "Verdict"