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 target bead:
- if the user supplied a bead id in the current request, use that bead
- if the user supplied freeform selector text, treat it as a selector or hint
- otherwise inspect bd ready --json and choose the best ready bead autonomously
Preferred bead choice order:
- first, a ready bead clearly related to the current repo context or recent planner discussion
- otherwise, the highest-priority ready bead
If bead choice is ambiguous, ask before claiming.
Claim the bead and run the executor workflow — every step in order:
- beads-claim
- writing-plans
- implementation
- systematic-debugging if blocked
- build-and-test — REQUIRED after implementation. Read the skill at and follow it. Do NOT skip this step.

Run exactly one full executor cycle for one bead.

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 target bead:
- if the user supplied a bead id in the current request, use that bead
- if the user supplied freeform selector text, treat it as a selector or hint
- otherwise inspect bd ready --json and choose the best ready bead autonomously
Preferred bead choice order:
- first, a ready bead clearly related to the current repo context or recent planner discussion
- otherwise, the highest-priority ready bead
If bead choice is ambiguous, ask before claiming.
Claim the bead and run the executor workflow — every step in order:
- beads-claim
- writing-plans
- implementation
- systematic-debugging if blocked
- build-and-test — REQUIRED after implementation. Read the skill at and follow it. Do NOT skip this step.

Executor Once