autonomous-loops

Coordinate autonomous Claude Code loops for multi-agent tasks from RFCs.

2|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/JaimeJunr/context-mode --skill autonomous-loops-jaimejunr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autonomous-loops
Source: https://github.com/JaimeJunr/context-mode/tree/main/.claude/skills/autonomous-loops
Command: npx skills add https://github.com/JaimeJunr/context-mode --skill autonomous-loops-jaimejunr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Patterns and architectures for running Claude Code loops autonomously, enabling scalable, repeatable automation of tasks with multi-agent coordination.

Core Features & Use Cases

  • Patterns and architectures for sequential pipelines, NanoClaw REPL, infinite agentic loops, continuous Claude PR loops, de-sloppify cleanup, and RFC-driven DAG orchestration.
  • Guidance on choosing the right loop architecture for problem complexity, enabling context persistence, merge queues, and robust error handling.
  • Real-world scenario: coordinate multiple agents to implement a feature described by RFC, with dependency DAG and quality gates.

Quick Start

Provide an RFC or spec and specify the desired loop pattern to start an autonomous Claude Code iteration.

Frequently Asked Questions about autonomous-loops

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

FAQPage Schema
How do I coordinate multiple Claude Code agents to implement a feature from an RFC?

Multi-agent orchestration from an RFC uses a dependency DAG to execute autonomous Claude Code loops across isolated context windows and per-unit worktrees. You provide the specification, select a loop pattern, and the system coordinates the agents automatically through a merge queue approval workflow.

What is the best way to structure autonomous Claude Code loops for complex feature development?

Autonomous Claude Code loops for complex feature development are structured using pattern selection across Sequential, NanoClaw, Infinite Agentic Loop, Continuous Claude, De-Sloppify, or Ralphinho architectures. The correct loop pattern is chosen based on problem complexity to enable context persistence and robust error handling.

Can I run RFC-driven DAG orchestration with separate context windows for each agent?

RFC-driven DAG orchestration supports cross-stage isolation with separate context windows and per-unit worktrees for each agent. This ensures autonomous multi-agent tasks maintain isolated environments while executing under a defined dependency graph with quality gates.

Does autonomous Claude Code execution support a merge queue approval workflow?

Autonomous Claude Code execution includes a merge queue approval workflow integrated into the dependency DAG execution. This allows coordinated multi-agent tasks to pass through defined quality gates before merging, ensuring robust error handling throughout the pipeline.

When do I need to use a dependency DAG for multi-agent task orchestration?

A dependency DAG is needed for multi-agent task orchestration when implementing complex features described by RFCs where multiple agents collaborate under defined dependencies. It structures the execution flow across isolated context windows and per-unit worktrees to maintain task order.

How do I choose between Sequential and Infinite Agentic Loop patterns for Claude Code?

Choosing between Sequential and Infinite Agentic Loop patterns depends on problem complexity and the need for context persistence. Sequential pipelines handle step-by-step tasks, while Infinite Agentic Loop and NanoClaw architectures support continuous, repeatable automation with robust error handling.