oz0 plugin procedure
For: Operators and developers looking up a command.
A plugin may declare a written procedure (procedure: {file, approved_by, approved_at, review_every} in oz0-plugin.yaml): a Markdown file with a # title and the sections ## Inputs, ## Steps (numbered), ## Checks and ## When to escalate, approved by the expert the manifest names.
This command generates, from it, the instructions of each agent whose instructions file does not exist yet or was generated before (a hand-written prompt is left alone), and a starter eval set per agent, evals/<agent>-procedure.yaml: a case that follows the steps and one per escalation condition, which must answer ESCALATE:. An eval file is rewritten only while it still starts with its generated line, so delete that line to keep your edits.
Run it again after every change to the procedure: lint warns when an agent's instructions were generated from another text, and when the procedure's review is due. The procedure tells the agent what to do; the tenant's tool policy, approvals and hooks decide what it may do.
Usage
oz0 plugin procedure [dir] [flags]
Flags
| Flag | Type | Default | Description |
|---|---|---|---|
--dry-run | bool | print what would be written instead of writing it |
Inherited flags
| Flag | Type | Default | Description |
|---|---|---|---|
--context | string | $OZ0_CONTEXT or <config dir>/orchestrator-zero/context.json | CLI context file written by server init |
--log-level | string | info | log level: debug, info, warn or error |
See all oz0 commands and the global flags.