loop-driver

What problem does it solve?

It standardizes an autonomous development loop that turns a candidate target into a shipped, CI-green change with an iteration retrospective and safe merge control.

Core Features & Use Cases

• Shared loop skeleton: Implements the common phases for autonomous iterations, including branch/plan, handoff to ship, an iteration-scoped /retro pass, merge handling, and loop re-arming or escalation.
• Quality gate for “nothing to ship” outcomes: Prevents shipping borderline work by treating “found something but not worth it” as a healthy iteration result, using the specialization’s Phase 1.5 bar.
• Operational safety invariants: Enforces one-change-per-PR and blocks merges before CI is green, with explicit pass-through of loop flags on re-wake.
• Use Case: Keep a repo’s engineering throughput moving by repeatedly selecting the next high-ROI target (issue label queue, complexity reduction audit, or risk/provability-driven bug hunting) and driving it through ship → retro → merge until idle escalation triggers.

Quick Start

Use the loop-driver indirectly by invoking one of its specializations (such as shovel-ready, kaizen, or bughunt) rather than calling loop-driver directly.