Menu
Multi-phase linear workflow — the agent narrates each phase to the user as it advances.
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.
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.
Integration of interviews and templates — interview answers drive frontmatter and body of a generated artifact. Demonstrates FR-017..025 end-to-end.
| name | multi-phase-auto-example |
| description | Multi-phase linear workflow — the agent narrates each phase to the user as it advances. |
| contributes | {"workflows":"./workflows"} |
A linear three-phase workflow (drafted → reviewing → filed) that
records note items at each step. No invariants gate the advances —
items are bookkeeping. This is the shape to copy when you want to track
work as a workflow walks through stages but you don't yet need
machine-checked preconditions.
The agent's job is to walk the workflow phase by phase, recording one
note item per phase and reporting progress to the user before moving
to the next phase. The point of this example is to show that
multi-phase auto workflows don't need to run silently — the human on
the other side of the chat wants to know what just happened.
Create the instance:
ix-flow run --path <this-dir> --json
While in drafted: ask the user what to draft (or pick something
reasonable from context), then record it:
ix-flow add-item <id> note --json '{"id":"n1","body":"<draft text>"}'
Report to the user: "Drafted: <draft text>. Advancing to
review." Then advance:
ix-flow advance <id> reviewing --json
While in reviewing: record a brief review note:
ix-flow add-item <id> note --json '{"id":"n2","body":"<review note>"}'
Report to the user: "Review notes: <review note>. Advancing
to filing." Then advance:
ix-flow advance <id> filed --json
While in filed (terminal): record a one-line filing note:
ix-flow add-item <id> note --json '{"id":"n3","body":"<filing note>"}'
Final report to the user: summarize what happened across all
three phases in 2–3 sentences and show
ix-flow status <id> --json.
Between every advance, the agent says one short, human-readable
sentence about what the workflow just captured and where it's going
next. That keeps the user oriented without spamming raw JSON. The
JSON state is always available via ix-flow status <id> --json if
the user wants the full picture.
Always pass --json to every ix-flow command. The phase argument
to advance is positional, not --to.
