Menu
Template variant chosen at render time from an item field (component_type). Demonstrates FR-019 variant resolution.
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 | variant-selection-example |
| description | Template variant chosen at render time from an item field (component_type). Demonstrates FR-019 variant resolution. |
| contributes | {"workflows":"./workflows"} |
The agent adds a component item that declares component_type. The
template's variant field is templates/${item.component_type}, so
the renderer reads from templates/fastapi-service/spec.md or
templates/react-lib/spec.md depending on the recorded item. When no
matching variant ships, the template falls back to templates/default/.
Run:
ix-flow run --path <this-dir> --jsonix-flow add-item <id> component '{"id":"c1","component_type":"fastapi-service"}' --jsonix-flow advance <id> rendered --jsonRe-create with a different component_type to see the other variant
selected.