Menu
Use at the start of an executor session to find and claim a ready bead. Do not invoke in planner sessions.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Remove a sibling git worktree created by `executor-task-worktree`, `executor-epic-task-worktree`, `executor-epic-sequential-worktree`, or `create-new-worktree` once follow-up work (review comments, screenshots, CI fixes) is done. Lists existing worktrees, confirms which to remove, verifies the branch is safe to drop (PR merged or user-approved), removes the worktree, prunes stale entries, and optionally deletes the local branch.
Run every ready child bead of one epic end-to-end, sequentially, on a single epic branch (epic/<epic-bead-id>). Each bead executes in a fresh headless `claude -p` session so context never carries between tasks; a failed bead is marked blocked and skipped (along with its dependents) and the run continues; finishes with one PR from the epic branch to the default branch. Use when the user wants to deliver a whole epic unattended as one branch and one PR instead of running one bead at a time.
Use when you want to deliver a whole epic unattended as ONE branch and ONE PR WITHOUT disturbing in-flight work in the main checkout. Runs every ready child bead of one epic sequentially in a fresh sibling git worktree checked out on the epic branch (epic/<epic-bead-id>) so the main working tree is never touched — each bead executes in its own fresh headless `claude -p` session (clean context per task), committing directly onto the single epic branch; a failed bead is marked blocked and skipped (along with its dependents) and the run continues; finishes with one PR from the epic branch to the default branch and leaves the worktree in place for follow-up (review comments, CI fixes). Use the `cleanup-worktree` skill to remove the worktree once the PR has landed.
Run a full executor cycle for one bead on a fresh feature branch off its parent epic branch (epic/<epic-bead-id>): stash any in-flight work, switch to the epic branch, pull, create feat/<bead-id>-<short-slug>, execute the bead end-to-end, then push and open a PR targeting the epic branch. Use when the user wants a single bead delivered as its own PR into an in-progress epic branch instead of main.
Run a full executor cycle for one bead in a fresh git worktree off its parent epic branch (epic/<epic-bead-id>): leaves the main working tree completely untouched, creates a sibling worktree at ../<repo>-feat-<bead-id>, executes the bead end-to-end, pushes, opens a PR targeting the epic branch, and leaves the worktree in place for follow-up work (review comments, screenshots, CI fixes). Use when an epic has its own integration branch and the main tree has active work that must not be disturbed. Use the `cleanup-worktree` skill to remove the worktree once follow-up work is done.
Delete local git branches whose upstream was removed from origin, and tear down any sibling git worktree still attached to them. Use when the user asks to clean up stale, pruned, merged, or deleted remote branches locally — including the worktrees the executor-*-worktree / create-new-worktree flows leave behind.
| name | beads-claim |
| description | Use at the start of an executor session to find and claim a ready bead. Do not invoke in planner sessions. |
Workflow position: Executor session, step 1 of 8. Next: writing-plans. See BEADS_WORKFLOW.md.
Find a ready bead and claim it for this session.
This is an executor skill. It must not be invoked in a planner session.Only invoke this skill when:
Do not invoke this skill when:
brainstorming or beads-planner
bd init --prefix <prefix> plus the repo scaffolding steps.bd ready --json
bd show <id> --json
executor-* orchestrator skills and the bead choice is unambiguous, proceed without an extra confirmation turnbd update <id> --status in_progress
writing-plans for the execution plan.executor-* orchestrator skill is driving the flow, it is valid to claim without confirmation when bead choice is unambiguous.in_progress before any implementation.