Loop Readiness Review

Use this skill before turning repeated agent work into a scheduled or recurring loop.

Use When

• a workflow may run on a cadence: cron, automation, /loop, GitHub Actions, or external scheduler;
• a runner will open worktrees, inspect CI, triage issues, update changelogs, watch PRs, or sweep dependencies;
• a SET bundle is being handed to a loop-capable orchestrator;
• a report-only loop is being promoted toward auto-fix or PR creation;
• you need to decide whether the loop is L0, L1, L2, or L3 ready.

Readiness Levels

• L0: not loop-ready; missing state, verifier, or human gate.
• L1: report-only; can read, summarize, and propose actions.
• L2: proposal-first; can create retained output, worktree changes, or draft PRs behind review gates.
• L3: governed loop; has state, isolation, verifier, budget, run log, rollback/escalation, and human-controlled settlement.