Workflow Steps
{"content":"{{\u003c tier level=\"sovereign\" note=\"Workflow steps combine Valdr actions, agents, reviews, decisions, and reusable workflows into one process.\" \u003e}}\n\nBuild workflows from actions, sessions, reviews, waits, approvals, outcome routes, and reusable workflows. Choose **Valdr Tools**, **Git**, **GitHub**, or **Command** for the action you need.\n\n{{\u003c cards \u003e}}\n {{\u003c card link=\"tool/\" title=\"Valdr Tools\" subtitle=\"Call supported Valdr actions from the workflow catalog\" icon=\"code\" \u003e}}\n {{\u003c card link=\"git/\" title=\"Git\" subtitle=\"Inspect repositories and integrate reviewed delivery\" icon=\"code\" \u003e}}\n {{\u003c card link=\"github/\" title=\"GitHub\" subtitle=\"Publish an approved exact branch as a pull request\" icon=\"code\" \u003e}}\n {{\u003c card link=\"command/\" title=\"Command\" subtitle=\"Run a trusted non-interactive shell command\" icon=\"terminal\" \u003e}}\n {{\u003c card link=\"session/\" title=\"Session\" subtitle=\"Launch or continue an agent session\" icon=\"terminal\" \u003e}}\n {{\u003c card link=\"review/\" title=\"Review\" subtitle=\"Launch an independent reviewer\" icon=\"check-circle\" \u003e}}\n {{\u003c card link=\"await-condition/\" title=\"Await Condition\" subtitle=\"Pause for expected evidence or an outcome\" icon=\"clock\" \u003e}}\n {{\u003c card link=\"human-gate/\" title=\"Human Gate\" subtitle=\"Require an operator approval or rejection\" icon=\"user\" \u003e}}\n {{\u003c card link=\"condition/\" title=\"Outcome route\" subtitle=\"Route work or repeat a bounded correction loop\" icon=\"switch-horizontal\" \u003e}}\n {{\u003c card link=\"subworkflow/\" title=\"Run Workflow\" subtitle=\"Compose an exact version of another workflow\" icon=\"arrows-expand\" \u003e}}\n{{\u003c /cards \u003e}}\n\n## Shared fields\n\nEvery step uses the same outer fields, plus configuration for its selected kind:\n\n| Field | Required | Purpose |\n| --- | --- | --- |\n| `key` | Yes | Unique name used by dependencies and expressions |\n| `name` | Yes | Human-readable label shown in Valdr UI |\n| `kind` | Yes | Selects the step behavior |\n| `needs` | No | Steps that must finish before this step can run |\n| `when` | No | Conditions that must pass, otherwise the step is skipped |\n| `inputs` | Depends on kind | Values supplied to a tool or child workflow |\n| `outputs` | No | Named values made available to later steps |\n| `onFailure` | No | Block, fail, or use a supported bounded loop |\n\n## Connect steps with expressions\n\n```yaml\n- key: load_task\n name: Load Task\n kind: tool\n tool:\n id: pm_task\n action: get\n inputs:\n taskKey: \"${workflow.inputs.taskKey}\"\n outputs:\n status: \"$.normalized.task.status\"\n\n- key: route_task\n name: Route Task\n kind: condition\n needs: [load_task]\n checks:\n - kind: value_equals\n value: \"${steps.load_task.outputs.status}\"\n equals: ready\n```\n\nThe producing step declares `status`; the consuming step names `load_task` in `needs` and reads the declared output.\n\n## Route with `when`\n\n```yaml\nwhen:\n - kind: value_equals\n value: \"${steps.review.outputs.outcome}\"\n equals: review_approved\n```\n\nAll `when` checks must pass. A false check skips the step; it does not fail the run.\n\n## Handle failure deliberately\n\n```yaml\nonFailure:\n action: block\n```\n\n- `block` stops at a recoverable point.\n- `fail` ends the run as failed.\n- `loop_back` is available only on an Outcome route and must set a maximum number of passes.\n\nValdr UI shows **Retry step** only when the current or latest attempt is failed or blocked and its error category is safe to repeat. Authored `retry.maxAttempts` is a reported attempt count; it neither caps manual recovery nor schedules automatic retries or backoff.\n\n## Validate before running\n\nThe Workflow Builder validates supported fields continuously and offers action-specific inputs and outputs. Diagnostics link back to the affected step or field. For YAML definitions, `pm_workflow validate` applies strict validation automatically:\n\n```text\npm_workflow { action: \"validate\", definitionYaml: \"...\" }\n```\n\n## Next step\n\nStart with [Valdr Tools](tool/) for the action-based MCP surface, use [Git](git/) for repository operations, [GitHub](github/) for pull-request publication, [Command](command/) for a trusted shell command, or choose another step above.","description":"Choose and configure the supported building blocks for Valdr workflows.","title":"Workflow Steps"}
Sovereign
Sovereign tier required. Workflow steps combine Valdr actions, agents, reviews, decisions, and reusable workflows into one process.
Build workflows from actions, sessions, reviews, waits, approvals, outcome routes, and reusable workflows. Choose Valdr Tools, Git, GitHub, or Command for the action you need.
Call supported Valdr actions from the workflow catalog
Inspect repositories and integrate reviewed delivery
Publish an approved exact branch as a pull request
Run a trusted non-interactive shell command
Launch or continue an agent session
Launch an independent reviewer
Pause for expected evidence or an outcome
Require an operator approval or rejection
Route work or repeat a bounded correction loop
Compose an exact version of another workflow
Shared fields
Every step uses the same outer fields, plus configuration for its selected kind:
| Field | Required | Purpose |
|---|---|---|
key | Yes | Unique name used by dependencies and expressions |
name | Yes | Human-readable label shown in Valdr UI |
kind | Yes | Selects the step behavior |
needs | No | Steps that must finish before this step can run |
when | No | Conditions that must pass, otherwise the step is skipped |
inputs | Depends on kind | Values supplied to a tool or child workflow |
outputs | No | Named values made available to later steps |
onFailure | No | Block, fail, or use a supported bounded loop |
Connect steps with expressions
- key: load_task
name: Load Task
kind: tool
tool:
id: pm_task
action: get
inputs:
taskKey: "${workflow.inputs.taskKey}"
outputs:
status: "$.normalized.task.status"
- key: route_task
name: Route Task
kind: condition
needs: [load_task]
checks:
- kind: value_equals
value: "${steps.load_task.outputs.status}"
equals: readyThe producing step declares status; the consuming step names load_task in needs and reads the declared output.
Route with when
when:
- kind: value_equals
value: "${steps.review.outputs.outcome}"
equals: review_approvedAll when checks must pass. A false check skips the step; it does not fail the run.
Handle failure deliberately
onFailure:
action: blockblockstops at a recoverable point.failends the run as failed.loop_backis available only on an Outcome route and must set a maximum number of passes.
Valdr UI shows Retry step only when the current or latest attempt is failed or blocked and its error category is safe to repeat. Authored retry.maxAttempts is a reported attempt count; it neither caps manual recovery nor schedules automatic retries or backoff.
Validate before running
The Workflow Builder validates supported fields continuously and offers action-specific inputs and outputs. Diagnostics link back to the affected step or field. For YAML definitions, pm_workflow validate applies strict validation automatically:
pm_workflow { action: "validate", definitionYaml: "..." }Next step
Start with Valdr Tools for the action-based MCP surface, use Git for repository operations, GitHub for pull-request publication, Command for a trusted shell command, or choose another step above.