القائمة
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.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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.
Run repeated manual executor cycles scoped to a single epic: pick the next ready descendant bead under that epic, execute it, then continue until the epic has no ready descendants or a blocker requires user input. Use when the user wants sequential epic progress without swarm coordination.
| name | beads-claim |
| description | 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. |
Workflow position: Manual executor session, step 1 of 7. Next: writing-plans. See BEADS_WORKFLOW.md.
Find a ready bead and claim it for this session.
This is a manual executor skill. It must not be invoked in a planner session or inside `execute-bead-worker`.Only invoke this skill when:
Do not invoke this skill when:
brainstorming or beads-plannerswarm-epic already assigned the bead to a worker
bd init --prefix <prefix> plus the repo scaffolding steps.bd ready --json
bd show <id> --json
executor-once, executor-loop, or executor-loop-epic and the bead choice is unambiguous, proceed without an extra confirmation turnbd update <id> --status in_progress
writing-plans for the execution plan.executor-once, executor-loop, or executor-loop-epic is driving the flow, it is valid to claim without confirmation when bead choice is unambiguous.in_progress before any implementation.swarm-epic owns claiming and closing for swarm runs. Workers do not call this skill.