Loop

Overview

Run the requested task as an iterative implementation pipeline. Implement the change, review the result, fix every actionable issue, and repeat until the review is clean or a real blocker prevents further progress.

Operating Rules

• Keep ownership with the orchestrator agent. Use reviewers for independent scrutiny, but the main agent decides what to fix, performs the fixes, and verifies the final state.
• Do not stop after finding review issues. Fix them, then run another review pass.
• Treat review findings as actionable unless they are demonstrably incorrect, duplicate, impossible with available context, or outside the user's requested scope.
• Do not claim the loop is complete while known correctness, security, data-loss, regression, build, test, or user-visible defects remain.
• Preserve unrelated user changes. If a review finding points at unrelated dirty work, call it out instead of rewriting it.
• When the harness supports todo lists, plans, or task checklists, create a clear, detailed todo list before implementation and keep item statuses current through every review and fix cycle.
• Keep the user updated during long loops, especially before substantial edits and after each review cycle.

Workflow