loop

1# /loop -- Bounded Foreground Loop
2 
3## Orientation
4 
5**Use when:** the user wants a visible repeat-until-pass cycle inside the
6current session, such as "loop until lint passes" or "try this up to three
7times and stop if tests still fail."
8 
9**Don't use when:** the work should run unattended across sessions (`/daemon`),
10on a clock (`/schedule`), on file changes (`/watch`), or as a metric-driven
11optimization experiment (`/experiment`).
12 
13In Claude Code, invoke `/citadel:loop` to select this skill explicitly.
14The host also has a timer-based `/loop` command with different semantics.
15 
16## Commands
17 
18| Command | Behavior |
19|---|---|
20| `/loop status` | Show all known Citadel loops with active/stopped grouping. |
21| `/loop inspect {id}` | Show one loop's contract, verifier, budget, runs, and stop reason. |
22| `/loop templates` | List built-in loop templates. |
23| `/loop plan --template {name}` | Create a loop contract from a template. |
24| `/loop run "{action}" --verify "{command}" --max {N}` | Run a bounded foreground loop. |
25| `/loop stop {id}` | Mark a loop stopped. |
26 
27## Protocol
28 
29### Step 1: Classify the loop
30 
31Determine which kind of loop the user requested:
32 
33| User intent | Route |
34|---|---|
35| Repeat within this active session | `/loop` |
36| Continue campaign across sessions | `/daemon` |
37| Run on a schedule | `/schedule` |
38| Watch PR checks/reviews | `/pr-watch` |
39| Watch files or marker comments | `/watch` |
40| Optimize a numeric metric | `/experiment` |
41…