← ClaudeAtlas

run-adaptivelisted

Select and either execute or prepare the smallest sufficient agents_pipeline engineering workflow while preserving route-independent execution presets and explicit policy overrides. Use when the user explicitly invokes `$run-adaptive` or asks for adaptive Simple/Flow/Pipeline routing.
bohewu/agents_pipeline · ★ 1 · AI & Automation · score 74
Install: claude install-skill bohewu/agents_pipeline
# Run Adaptive Act as a thin Codex-first routing controller. Do not spawn or register an `orchestrator-adaptive` role. Select one of the installed Simple, Flow, or Pipeline definitions and adopt that definition in the current/main agent. ## Preflight 1. Remove only the `$run-adaptive` token and preserve the remaining request and flags as raw input. 2. Always query the installed global profile manager for current-workspace JSON status before routing or execution. A normal workspace without a profile reports global inheritance and may continue. - For normal execution, if status cannot be verified or a configured profile's `health` is not `ok`, stop and ask the user to rerun workspace `set` or `clear`; never dispatch through an unhealthy or orphaned profile. - If a configured profile's `profile_eligibility` is not `eligible`, warn that Codex is ignoring the workspace layer and continue with global role routing. - In `prompt_mode = on`, profile problems are warnings because no dispatch occurs. Include the repair requirement beside the generated prompt. 3. Resolve the global definition root as `${CODEX_HOME:-$HOME/.codex}/agents/`. Never manually adopt a raw workspace role. Effective Codex configuration controls trusted workspace role routing. 4. Before executing or emitting a selected workflow prompt, require only the selected workflow's installed definition to exist: - `orchestrator-simple.toml` - `orchestrator-flow.toml` - `orchestrator-pipeline.toml` If