autonomous-loops

Orchestrate autonomous Claude Code loops for iterative software development.

Updated Apr 29, 2026
One-click install
npx skills add https://github.com/pgm1980/stryker-netx --skill autonomous-loops-pgm1980
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autonomous-loops
Source: https://github.com/pgm1980/stryker-netx/tree/main/.claude/skills/autonomous-loops
Command: npx skills add https://github.com/pgm1980/stryker-netx --skill autonomous-loops-pgm1980

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Autonomous development often fails because LLM-driven loops lack clear architectures for iteration, coordination, context persistence, and quality gates, causing duplicated work, missed failures, or stalled progress.

Core Features & Use Cases

  • Loop Pattern Library: Provides practical architectures ranging from simple sequential pipelines to multi-agent RFC-driven DAG orchestration for larger changes.
  • Context & State Management: Covers techniques like persistent REPL sessions and cross-iteration context bridging (e.g., shared notes) to prevent “lost progress.”
  • Quality Gates & Recovery: Includes reviewer/de-sloppify passes, CI-failure recovery patterns, and merge-queue-style eviction to handle conflicts and test failures safely.

Use case example: Turn a multi-day feature into a continuous PR loop that iteratively implements changes, runs CI, auto-fixes failures, and merges when checks pass—using shared notes to preserve progress across iterations.

Quick Start

Start an autonomous PR-style loop by directing the agent to implement a feature, run CI checks after each iteration, and continue until it produces an explicit completion signal.

Frequently Asked Questions about autonomous-loops

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

FAQPage Schema
How do I set up an autonomous coding loop for continuous PR generation?

An autonomous coding loop iteratively implements feature changes, runs CI checks after each pass, auto-fixes failures, and merges when quality gates pass. You direct the agent to implement a feature and continue until it produces an explicit completion signal.

How does cross-iteration context persistence prevent lost progress in multi-agent workflows?

Cross-iteration context persistence uses shared notes and persistent REPL sessions to bridge state across research, plan, implement, test, and review stages. This prevents duplicated work and stalled progress by maintaining context throughout the autonomous loop.

What's the best way to handle CI failure recovery in autonomous development pipelines?

CI failure recovery patterns automatically detect test failures during loop iterations, trigger reviewer and de-sloppify passes to fix issues, and apply merge-queue-style eviction to handle conflicts safely before continuing the autonomous workflow.

When do I need parallel multi-agent DAG orchestration instead of a sequential pipeline?

Parallel multi-agent DAG orchestration is needed for larger changes requiring RFC-driven coordination across multiple agents, while sequential pipelines handle simpler iterative tasks. Choose DAG orchestration when changes demand structured, concurrent task execution.

Why do autonomous LLM-driven loops stall or duplicate work during software development?

Autonomous loops stall or duplicate work because they lack clear architectures for iteration, coordination, context persistence, and quality gates. Without explicit loop termination controls and cross-iteration state bridging, progress is lost between cycles.

Can I use persistent REPL sessions to maintain state across autonomous loop iterations?

Yes, persistent REPL sessions maintain execution context and shared notes across autonomous loop iterations. This context bridging technique prevents lost progress during specification-driven generation and multi-stage software development workflows.