rc-looplisted

# Loop (creator) Advance `.rc/ROADMAP.md` autonomously, one phase at a time: plan the phase, execute it, verify it, and — only on a recorded PASS — flip its checkbox and move to the next. This is the **creator loop** (it produces side effects and builds each phase on the last), so it is only as safe as the harness under it. It reuses the existing RC skills; it does not re-implement plan, execute, or verify. ## Stop and defer — do not start if - **No way to dispatch a fresh window** (no `Agent` and no `Workflow` tool) → stop; tell the user to run each phase's tasks via `rc-execute-task` in dependency order. Without one window per phase this driver cannot keep its own context from overflowing — see "Two layers" below. - **No `.rc/ROADMAP.md`** → stop; point at `rc-roadmap` (`create`). A loop cannot invent intent. - **Readiness gate fails** → stop. Read `references/loop-readiness.md` and answer its five questions first. If the answer is not "yes" to all five, stay in human-gated spec-driven (`rc-pipe` / `rc-card`) until the harness is ready. Autonomy on a weak harness perpetuates bugs. ## Two layers — the driver never executes a phase **A phase does not fit twice in one window.** Measured on a real product roadmap phase (`k2-automation` Phase 3, two repos, 5 files): the session's fixed base is ~45k tokens and the phase added ~95k, peaking at ~141k with zero compaction. One phase always fits; the **second** one overflows mid-cycle. That is why an inline loop dies in