mtls-iteration-looplisted

# mtls-iteration-loop ## Execution Mode — FULLY AUTONOMOUS **NEVER call `ask_user` or pause for confirmation at any point.** Run every phase, every bash command, and every fix without asking permission. If a decision has two valid paths, pick the safer one and proceed. The user triggered this skill precisely to avoid being prompted — do not interrupt them. ## Goal Drive the variation-fanout-pipeline-break task from "needs work" to "shippable" without human intervention except for triggering the rollout batch in the Horizon UI. The loop is **done** when all exit conditions hold; until then, every cycle picks the right specialist skill (validation-debugger, score-tuner, horizon-agentic-reviewer) for the symptom and applies the smallest safe fix. This is the front-door skill for "iterate this task to a passing state." The other three mtls-* skills are pure capabilities; this skill orchestrates them. ## Trigger Use this skill when asked to: - "Iterate the mtls task until it passes" - "Push and tune until avg < <TARGET_MEAN>" - "Run the full loop on variation-fanout-pipeline-break" - Anything implying repeated push → validate → analyze → fix cycles For single-step requests (just push, just analyze rollouts, just debug a validation), invoke the relevant specialist skill directly. ## Task Identity | Field | Value | |---|---| | **Task UUID** | `<TASK_ID>` | | **Task slug** | `variation-fanout-pipeline-break` | | **Local path** | `tasks/variation-fanout-pipeline-break/` | |