Name: Executor Loop
Author: doviettung96

Run repeated manual executor cycles bead-by-bead until the queue is exhausted or a blocker requires user input.

For epic-scoped multi-agent work with coordinator-owned bead state, prefer swarm-epic.

Steps

If the current repo is not initialized for Beads, stop and tell the user to run the template bootstrap script or at minimum bd init --prefix <prefix> plus the repo scaffolding steps.
Determine the first bead:
- if the user supplied a bead id in the current request, start there
- if the user supplied freeform selector text, treat it as a selector or hint for the first bead
- otherwise inspect bd ready --json and choose the best ready bead autonomously
Run one full executor cycle for that bead by invoking every step in order:
- beads-claim
- writing-plans
- implementation
- systematic-debugging if blocked
- build-and-test after implementation; read .codex/skills/build-and-test/SKILL.md and follow it
- or

Run repeated manual executor cycles bead-by-bead until the queue is exhausted or a blocker requires user input.

For epic-scoped multi-agent work with coordinator-owned bead state, prefer swarm-epic.

If the current repo is not initialized for Beads, stop and tell the user to run the template bootstrap script or at minimum bd init --prefix <prefix> plus the repo scaffolding steps.
Determine the first bead:
- if the user supplied a bead id in the current request, start there
- if the user supplied freeform selector text, treat it as a selector or hint for the first bead
- otherwise inspect bd ready --json and choose the best ready bead autonomously
Run one full executor cycle for that bead by invoking every step in order:
- beads-claim
- writing-plans
- implementation
- systematic-debugging if blocked
- build-and-test after implementation; read .codex/skills/build-and-test/SKILL.md and follow it
- or

Executor Loop