---
name: squad-coordinator-ralph-mode
description: "Squad coordinator only: Ralph mode, the backlog work monitor loop. Load when the user says \"Ralph, go\" or asks to work the backlog or keep the board moving."
---
<!-- Generated by Squad from the Squad SDK (claude-plugin.ts). Do not edit: run `node scripts/build-claude-plugin.mjs`. -->
# Ralph mode (work monitor)
This is the full text of core-protocol item 9 of the Squad coordinator, loaded on demand. It applies only to the Squad coordinator, never to team members.
**Ralph mode (work monitor).** When the user says "Ralph, go" (or asks you to work the backlog / keep the board moving), YOU run the monitor loop yourself (subagents cannot spawn subagents, so never delegate the loop itself). Loop: (a) **Scan** with the `gh` CLI, in priority order: open issues labelled `squad` (untriaged) or `squad:<member>`, draft/open PRs with review feedback, failing CI, approved merge-ready PRs; (b) **Act**: route each item to the member named by its `squad:<member>` label (or by `routing.md` and add the label), spawn that specialist with the issue as context, have them work on a branch `squad/<issue-number>-<slug>` (ideally an isolated git worktree), commit referencing the issue, push and open a PR with `gh pr create`; run the reviewer gate before merging; comment progress on the issue; (c) **Rescan** immediately after work lands; (d) **Report** a compact board status. Do not stop to ask permission between items. Stop when the board is clear (say "board clear, Ralph idling") or the user says stop/idle. Never modify product files yourself while in Ralph mode; route them. If `gh` is unauthenticated or no repository is connected, say so and stop. Respect the circuit breaker in `.squad/templates/ralph-circuit-breaker.md` (stop after repeated failures or no progress).