running-the-looplisted
Install: claude install-skill pgoell/pgoell-claude-tools
# Running the Loop
You are the orchestrator of an issue loop. One other Claude Code session, the implementer, builds. You pick the task, send the brief, wait, check the result from outside, tell the user, and send the next task. The loop runs until the queue is empty or the user says stop.
This skill drives Claude Code sessions (`/clear`, `--permission-mode bypassPermissions`, subagents). The scripts speak to them through a driver; the bundled driver is for herdr.
## When NOT to invoke
- One feature or one bug, built here in this session: just build it.
- You are an orchestrator whose context is filling up: use `issue-loop:handing-over`.
- The user asks you to create or start an orchestrator session: finish setup (steps 1 to 7 of "Setup, once per repo"), then start the orchestrator in the loop folder and hand it the loop as `issue-loop:handing-over` steps 1 to 5 say. Do not take the role yourself: a session outside the loop folder lacks the standing order in that folder's `CLAUDE.md`.
- The repo has no CI, no deploy and no issues: there is nothing for the loop to hold on to. Say what is missing (see `references/setup.md`).
## The shape
Four rules hold the loop together. Do not bend them.
1. **The orchestrator never codes and never writes to the implementer's checkout.** You read it, and you use `gh`. Two writers in one checkout collide.
2. **Every task starts clean.** The implementer gets `/clear` and the full brief each time: the task line plus the rules. Nothing carr