メニュー
Run repeated manual executor cycles bead-by-bead until the ready queue is exhausted or a blocker requires user input. Use when the user wants sequential autonomous progress without swarm coordination.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | executor-loop |
| description | Run repeated manual executor cycles bead-by-bead until the ready queue is exhausted or a blocker requires user input. Use when the user wants sequential autonomous progress without swarm coordination. |
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.
bd init --prefix <prefix> plus the repo scaffolding steps.bd ready --json and choose the best ready bead autonomouslybeads-claimwriting-planssystematic-debugging if blockedbuild-and-test after implementation; read .codex/skills/build-and-test/SKILL.md and follow itverification-before-completion or requesting-code-reviewbeads-closebd ready --json again and choose the next best ready bead using the same preference order.Use at the start of a manual executor session to find and claim a ready bead. Do not invoke in planner sessions or inside swarm workers.
Use after implementation and verification are complete to close the bead, create follow-up beads, and commit the updated `.beads/` state. This is the final step of a manual executor session.
Break a discussed or approved problem into Beads epics and tasks with clear dependencies and validation work. Use when the user wants to turn a problem statement, planning discussion, or approved execution plan into a Beads structure instead of ad-hoc TODOs.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements, and design before implementation.
Use after implementing changes to run the exact verification commands from the current execution plan. This stage-1 version is intentionally generic and should be specialized per repo once the runtime workflow is clear.
Execute one assigned bead inside a swarm coordinated by swarm-epic. Use only when a coordinator has assigned the bead, file scope, and verification contract; the worker implements, verifies, and reports without mutating bead state.