continuous-agent-loop

Orchestrates autonomous agent loops with quality gates, evals, and recovery controls.

1|Updated Oct 11, 2025
One-click install
npx skills add https://github.com/ibytechaos/claude --skill continuous-agent-loop-ibytechaos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: continuous-agent-loop
Source: https://github.com/ibytechaos/claude/tree/main/plugins/everything-claude-code/skills/continuous-agent-loop
Command: npx skills add https://github.com/ibytechaos/claude --skill continuous-agent-loop-ibytechaos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Running autonomous AI agents in continuous loops often leads to churn without progress, repeated failures on the same root cause, stalled merge queues, and uncontrolled cost escalation. This Skill provides structured patterns for selecting, combining, and recovering continuous agent loops so they stay measurable and controllable. ## Core Features & Use Cases - Loop Selection Flow: Routes work to the right loop type—continuous-pr for strict CI/PR control, rfc-dag for RFC decomposition, infinite for exploratory parallel generation, or sequential as the default. - Combined Production Pattern: Recommends a stack of RFC decomposition, quality gates, an eval loop, and session persistence for production-grade autonomy. - Failure Recovery: Defines concrete recovery steps—freeze the loop, run a harness audit, reduce scope to the failing unit, and replay with explicit acceptance criteria. - Use Case: A team running an overnight autonomous coding agent notices it retrying the same failing test for hours. They apply the recovery pattern: freeze the loop, audit the harness, narrow scope to the failing unit, and restart with explicit acceptance criteria. ## Quick Start Ask the agent to set up a continuous agent loop with quality gates and evals for your current coding task, choosing the appropriate loop type from the selection flow.

Frequently Asked Questions about continuous-agent-loop

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run an autonomous coding agent in a continuous loop?

Choose a loop type based on your control needs: continuous-pr for strict CI/PR control, rfc-dag for RFC decomposition, infinite for exploratory parallel generation, or sequential as the default. Then layer in quality gates, an eval loop, and session persistence for production use.

What is the recommended stack for production agent loops?

The recommended production stack combines RFC decomposition via ralphinho-rfc-pipeline, quality gates via plankton-code-quality and /quality-gate, an eval loop via eval-harness, and session persistence via nanoclaw-repl.

How do I recover when an agent loop keeps failing?

Freeze the loop, run /harness-audit to diagnose the harness, reduce scope to the failing unit, and replay with explicit acceptance criteria. This addresses common failure modes like repeated retries on the same root cause.

What are common failure modes of autonomous agent loops?

The documented failure modes are loop churn without measurable progress, repeated retries with the same root cause, merge queue stalls, and cost drift from unbounded escalation. Each is mitigated through quality gates, evals, and the defined recovery procedure.

When should I use continuous-pr versus rfc-dag loops?

Use continuous-pr when you need strict CI/PR control over agent output. Use rfc-dag when work must first be decomposed through an RFC process into a dependency graph of tasks.