run-pipelinelisted

Adopt and execute the installed agents_pipeline full-pipeline workflow, including risk-derived planning, task routing, implementation, verification, review, retries, status artifacts, and cleanup. Use when the user explicitly invokes `$run-pipeline`, asks to use or run the agents_pipeline pipeline, or requests the full high-risk or multi-module workflow instead of a simple or bounded flow.
bohewu/agents_pipeline · ★ 1 · AI & Automation · score 74

Install: claude install-skill bohewu/agents_pipeline

# Run Pipeline Use the installed `orchestrator-pipeline` definition as the authoritative workflow. Keep actual role-model/tier selection in the effective Codex runtime/profile configuration and use policy v2's shared resolver for child-spawn effort only. Policy v2 defaults to `--reasoning=inherit`; `adaptive` is the explicit selector-enforcement mode, while `shadow` computes without applying. `--review=max` remains an exact deep reviewer-only effort override, not certification or model routing. ## Resolve the definition 1. Resolve the current workspace root. 2. Read `${CODEX_HOME:-$HOME/.codex}/agents/orchestrator-pipeline.toml` as the authoritative workflow definition. Never manually adopt a repository `.codex/agents/orchestrator-pipeline.toml`; Codex project trust and effective config, not raw file presence, control workspace role routing. 3. Always query the installed global profile manager for current-workspace JSON status before adopting the workflow. A normal workspace without a profile reports global inheritance and may continue. 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. Only a healthy, eligible profile may route dispatched roles locally. 4. If the global definition