ccc-relay

$ccc-relay — Cross-Session Loop Chaining

$ccc-loop iterates inside one session. $ccc-relay chains separate sessions: an always-on spec loop hands its result to a build loop, which hands to a review loop, which hands to merge — each a distinct, independently-gated loop that launches the next automatically when its own stop condition is met. This is the "Finn Loop" pattern: not one agent looping, but a relay team of loops passing a baton.

$ccc-relay composes three primitives instead of re-implementing them — read those skills for the mechanics this one orchestrates:

• ccc-loop — the loop taxonomy, the should-loop gate, the state-file convention, verifier-separation. Each link in a relay is one loop from that taxonomy.
• ccc-fleet — parallelism within a link (fan out the build across worktrees). A relay is sequential across links; a fleet is parallel within one.
• commands/ccc-spawn.md (/spawn) — the CLI mechanism for launching the next session as a peer when you're at a terminal.

What it is

A relay is a directed chain of loop sessions. Each link is a real loop (turn/goal/time/proactive — see ccc-loop), runs to its own stop condition, then triggers the next link and exits. No human re-prompts between links.

The canonical chain:

spec loop  ──▶  build loop  ──▶  review loop  ──▶  merge (human GO)
 $ccc-plan       $ccc-build        $ccc-review       $ccc-ship
 + /goal         + /goal           + /goal           (gated — never auto)

Baton pass, per link:

1. Link A runs as a normal gated loop (e.g. a /goal spec loop: "produce a plan file with acceptance criteria, stop after 5 tries").
2. On convergence, Link A writes its result and a completion marker into .claude/loop-state/<relay-name>.json — it sets relay.phase to done and fills the handoff block.
3. The next link is launched by whichever mechanism fits the surface:
   • Cloud / unattended → /schedule fires the next loop (survives a closed laptop — the right default for a real relay).
   • Cowork Desktop → a spawn_task chip offers to spin the next link into its own session (one click).
   • CLI → /spawn launches the next session as a peer (see ccc-spawn.md).
4. Link B consumes the handoff block as its brief, runs its own gated loop, and repeats the pass — through review, then stops at merge for an explicit human GO.