rc-roadmaplisted

# Loop Roadmap `.rc/ROADMAP.md` is the **source of truth an autonomous loop reads each iteration**. It holds high-level phases (epics), not task detail — a phase is planned in full only when the one before it is done, because a creator loop builds on what already exists and cannot plan the far future blind. Authoring and reordering phases is a **human decision**: the loop executes intent, it does not invent it (a loop resolves *how*, never *whether*). Confirm the roadmap with the user before a loop consumes it. Read `references/roadmap-format.md` before creating or editing the file — it holds the exact template, the checkbox legend, and the invariants a loop depends on. ## create — author or extend the roadmap 1. Establish the project's `.rc/` base (nearest `.rc` walking up; default `./.rc`). 2. If `.rc/ROADMAP.md` is missing, do a brief exploration (or read the PRD/TechSpec under `.rc/tasks/` if present) and draft phases at **epic** granularity — each ends in something runnable, with a one-line **`> Done when:`** gate. 3. State the **hard dependency order** and mark that phases never run in parallel. 4. **Confirm the phase list and order with the user** before any loop runs. This is the intent gate; do not skip it. When a loop exhausts (see `rc-loop`), the human re-enters here to research and append the next batch of phases — the roadmap grows in stages, it is not written all at once. ## next — resolve the next actionable phase Return the first phase whose ch