with one click
hitl-gate-example
Terminal advance is gated by first-class CLI HITL state.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Menu
Terminal advance is gated by first-class CLI HITL state.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Smallest possible workflow skill — two phases joined by one auto transition.
Multi-phase linear workflow — the agent narrates each phase to the user as it advances.
Build a directed graph of nodes; the core `acyclic` invariant gates the terminal advance.
One question, one phase, interview.complete gates the transition. Demonstrates FR-022, FR-023, FR-024 happy path.
Question bank exercising every supported answer type — text, list<text>, enum, bool, int — with minItems and required flags. Demonstrates FR-022, FR-023 validation paths.
Two-phase workflow with followUpIf re-surfacing a question downstream. Demonstrates FR-024-AC-8 advisory channel.
| name | hitl-gate-example |
| description | Terminal advance is gated by first-class CLI HITL state. |
| contributes | {"workflows":"./workflows"} |
The workflow definition marks staged -> published with defaultGate: hitl.
The CLI owns that gate: an advance attempt creates an open gate token, the
agent asks the human for approval, ix-flow ack records the approval, and
the next advance completes the transition.
Always pass --json to every ix-flow command. After every write, read
next_actions and run the command it gives you. If an advance returns
state: "gate_deferred", ask the human for approval in plain English, then
run the provided ack command with the human as reviewer and their response as
the note.