ix-flow

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.

Integration of interviews and templates — interview answers drive frontmatter and body of a generated artifact. Demonstrates FR-017..025 end-to-end.

Custom invariant requires at least one greeting before advancing.

Custom invariant validates that every report item carries a non-empty `summary` field before the next phase.

Terminal advance is gated by first-class CLI HITL state.

One skill ships two related workflows; the user disambiguates by passing the workflow name positionally to `run --path`.

Minimal artifactTemplates declaration — phase-entry renders one Markdown file from a template with variable substitution. Demonstrates FR-017, FR-018, FR-019.

Template variant chosen at render time from an item field (component_type). Demonstrates FR-019 variant resolution.

Author a new Agent IX workflow — scaffold a flow (def.yaml) and the skill (SKILL.md) that runs it. Use when asked to create, author, or scaffold an ix-flow workflow.

Collect a request through a short interview, then draft and finish.

Run an Agent IX workflow with ix-flow — create a run and drive it through its phases, pausing at human gates for approval. Use when asked to run, start, continue, or resume an ix-flow workflow.

Drive a change from draft through review to release.