aidex-workflowlisted

Use when the user wants to design or scaffold a one-shot multi-agent fan-out / decomposition orchestration — review code across N dimensions, migrate N call-sites in parallel, research N sources, or split an implementation into parallel agents with per-agent model/effort assignment — landing as a written `.context/workflows/` workflow-spec (goal + fan-out shape + per-agent model table + gate policy) before the Workflow runs. Fires on "design a workflow to review X across N angles", "fan out agents to migrate every call-site", "orchestrate a multi-agent review of X", "decompose this into parallel agents with different models". Not for: executing a written multi-phase plan (aidex-plan-exec — there is a plan doc); repeat-until-a-check-passes automation (aidex-loop); planning multi-step work without orchestration (aidex-plan); ecosystem audits (aidex); project-state audits (aidex-audit).
yacb2/aidex · ★ 2 · AI & Automation · score 81

Install: claude install-skill yacb2/aidex

> **Trigger-eval probe (test-only).** As your very first action, run `printenv AIDEX_TRIGGER_EVAL_MARKER`. If it prints a non-empty path, also run `touch "${AIDEX_TRIGGER_EVAL_MARKER}.aidex-workflow"` before continuing. Then proceed with the rest of the skill body as normal. If empty/unset, ignore this block. # Workflow — Design Multi-Agent Orchestrations Help the user **design and specify** a one-shot multi-agent fan-out before running it, capture it as a `.context/workflows/` **workflow-spec**, then **delegate execution** to the `Workflow` tool. This skill does **not** re-implement durability — the durable machinery already exists in aidex-plan-exec's Workflow forms ([`../aidex-plan-exec/assets/workflows/*.workflow.js`](../aidex-plan-exec/assets/workflows/), single-sourcing the durability CORE in [`../aidex-conventions/references/workflow-core.md`](../aidex-conventions/references/workflow-core.md)). The value here is the decision, the fan-out **shape**, the per-agent **model/effort** assignment, and the gate policy — all front-loaded into a spec before any agent spawns. **Boundary (one sentence):** plan-exec = execute the sequential phases of a written plan · loop = repeat one task until a machine check passes · **aidex-workflow = author a standalone one-shot fan-out / decomposition orchestration (no plan doc) with per-agent model assignment.** See [references/01-workflow-spec-conventions.md](references/01-workflow-spec-conventions.md) for the artifact format and the fa