← ClaudeAtlas

aidex-looplisted

Use when the user wants to design, scaffold, or choose an agentic LOOP that repeats one task until a check passes — iterate-until-green automation, a long-running unattended build, or picking which loop engine fits — landing as a written `.context/loops/` loop-spec (goal + verifiable stop condition + guardrails + chosen engine) before the loop runs. Fires on "design a loop for X", "set up a loop to keep building until tests pass", "make a loop that iterates until green", "loop until the build is clean", "which loop should I use". Not for: one-shot multi-agent fan-out across N different targets, which repeats nothing (aidex-workflow); executing an existing loop right now (hand off to the ralph-loop plugin, /loop, or /goal); one-off tasks with no stop condition; planning multi-step work without a loop (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-loop"` before continuing. Then proceed with the rest of the skill body as normal. If empty/unset, ignore this block. # Loop — Design Agentic Loops Help the user **design and specify** an agentic loop before running it, capture it as a `.context/loops/` **loop-spec**, then **hand off execution** to an existing engine. This skill does **not** implement a loop runner — three mature engines already exist (`/goal`, `/loop`, the `ralph-loop` plugin) plus headless `claude -p`. The value here is the decision, the spec, and the guardrails. See [references/01-loop-engines.md](references/01-loop-engines.md) for the engine matrix and guardrails, and [references/02-loop-spec-conventions.md](references/02-loop-spec-conventions.md) for the artifact format. ## Default autonomy On run start, apply [Mode A autonomy](../aidex-conventions/references/autonomy-conventions.md) automatically — do not wait for the user to grant it. Questions live in the initial alignment moment only; after that the run proceeds start-to-finish per the shared canon (deny/pre-authorized/mandated/autonomous). See "Run doctrine" below for how this applies once a loop is running. --- ## Sub-actions Dispatch by first argument: | Command | Backed by | Purpose | |---|---|---| | `/aidex-loop` | — | Show help + list existing `.cont