Patterns and architectures for autonomous Claude Code loops — from simple sequential pipelines to RFC-driven multi-agent DAG systems.
The `autonomous-loops` skill provides structured patterns and architectures for running Claude Code in autonomous loops, enabling developers to automate complex workflows without constant human oversight. It addresses the challenge of orchestrating sequential and parallel AI tasks, ranging from simple step-by-step pipelines to sophisticated multi-agent DAG systems driven by RFCs. By formalizing loop structures, this skill helps maintain consistency, context persistence, and orderly progression of tasks across iterative cycles.
Core capabilities include a spectrum of loop patterns such as sequential pipelines, interactive persistent sessions (NanoClaw REPL), continuous PR loops, and RFC-driven DAG orchestration. Each pattern offers distinct complexity levels and suitability, from daily development steps to large-scale multi-agent coordination with merge queues. Additional features like context isolation per step, cleanup passes (De-Sloppify), and quality gates ensure robust and reliable autonomous execution. The skill also supports variations with model routing for specialized tasks, allowing for flexible integration into diverse workflows.
This skill is ideal for developers, teams, or organizations aiming to implement autonomous development pipelines or continuous integration processes. It is particularly useful for building CI/CD-style loops, coordinating parallel agents, maintaining context across iterations, and enforcing quality control in automated development tasks. Its target users are those seeking to scale AI-driven coding and workflow automation efficiently, from individual contributors to multi-unit development teams.
Begin by choosing the loop pattern that fits your workflow complexity, from sequential pipelines for simple tasks to RFC-driven DAGs for multi-agent orchestration. Implement steps using `claude -p` for non-interactive execution or the NanoClaw REPL for interactive sessions.
The skill is retained for backward compatibility in v1.8.0, but new development loops are recommended to use `continuous-agent-loop` to ensure support and access to updated features.
Yes, patterns like the Continuous Claude PR Loop and RFC-Driven DAG are designed for extended iterative workflows with multi-day timelines, incorporating CI-style gates and merge coordination.
Negative instructions within a single `claude -p` step can be risky. It is safer to implement cleanup steps using the De-Sloppify pattern. Each step is isolated, so context does not persist between non-interactive calls unless explicitly managed.
Yes, model routing is supported. For example, you can use one model optimized for deep reasoning for research steps and another for fast implementation, allowing specialized task handling within the same pipeline.
Quick Setup:
.claude/skills/Repository
affaan-m/everything-claude-code