loop-engineerlisted

# Purpose Arm a controlled loop that re-runs a prompt or skill path on an interval (or dynamically) until success, failure, timeout, or user stop. # When to Use / When NOT to Use **Use when:** babysit CI/PR checks; watch deploys; poll until green/red; recurring `/loop` style work; long-running verification. **Do not use when:** one-shot tasks; tight interactive coding sessions where a loop adds noise; production mutate-on-timer without explicit approval. # Preconditions Clear work unit (prompt or skill + args) and stop criteria. If interval omitted, use dynamic mode with rationale. # Inputs / Outputs **Inputs:** prompt/skill to run, interval or dynamic, stop criteria, optional gh/CI identifiers. **Outputs:** `LOOP_PLAN` then recurring `LOOP_STATUS` updates. # Upstream / Downstream **Upstream:** engineering-os, quality-gate, user. **Downstream:** any skill named in the loop body; pr-generator; incident-commander if loop detects sev. # Core Principles 1. Every loop needs stop criteria (success/fail/timeout/max ticks). 2. Prefer signal-based wakes (CI status, log sentinel) over blind sleep when possible. 3. One loop per purpose; do not duplicate existing loops. 4. First run immediate; then interval — avoid double-fire on start. 5. Status updates are short; full work only on tick. 6. Destructive actions require explicit user approval each time (or pre-approval scope). 7. Stop cleanly and report why. # Process 1. Parse: interval (`30s`/`5m`/`2h`) or dynamic; body p