loopifylisted

# loopify ## Overview In one line, for anyone: **Hand Claude a job that repeats. Come back to a log of what every tick did, not a loop you have to babysit.** Prepare the best possible standing loop in THIS session, then hand the user one line to paste into Claude Code's built-in `/loop`. loopify never starts the loop. **loopify produces TWO artifacts, not one — and they have fixed names. Use these words everywhere:** 1. **The brief — a file.** A *standing* loop brief at an absolute path under `.loop/`. The loop re-reads it at the start of every tick. It is never archived, moved, deleted or rewritten by a run; runs write only under the **state directory** next to it. 2. **The line — a string.** One short `/loop [interval] Run one cycle of <ABSOLUTE PATH> · …` line the user pastes. The brief's path rides inside it. Also: **a tick** is one fire of the loop; **a cycle** is one pass of the brief per tick. Never call the line a "condition" — that word implies an evaluator, and **`/loop` has no evaluator**: nothing judges "done". The per-tick definition of done plus the tick log (`TICKS.md`) ARE the proof. **Two phases, never mixed.** PREPARE (here, now): understand the project, scope ONE cycle, research, lock the genuine decisions with one question batch, author the brief, write and lint the line, hand off. RUN (later, every tick): the user pastes the line; each tick re-reads the brief, runs exactly one cycle, logs it, then schedules the next tick or stops. You are