القائمة
One skill ships two related workflows; the user disambiguates by passing the workflow name positionally to `run --path`.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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 | multi-workflow-example |
| description | One skill ships two related workflows; the user disambiguates by passing the workflow name positionally to `run --path`. |
| contributes | {"workflows":"./workflows"} |
A skill that contributes two workflows from the same directory. When
multiple definitions live under workflows/, you must pick one
explicitly when creating an instance:
ix-flow run --path examples/skill-with-invariant/04-multi-workflow report
ix-flow run --path examples/skill-with-invariant/04-multi-workflow publish
Both workflows share a single scripts/invariants.js. Invariant names
are shared across all workflows in the skill — pick names like
report.has_findings and publish.has_target to avoid collisions.