メニュー
Run a planner-only Beads session: brainstorm, produce or confirm an execution plan, get user approval, then create beads and stop. Use when the user wants to turn a current problem or topic into Beads without implementing.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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.
| name | plan-beads |
| description | Run a planner-only Beads session: brainstorm, produce or confirm an execution plan, get user approval, then create beads and stop. Use when the user wants to turn a current problem or topic into Beads without implementing. |
Run a planner-only Beads session.
bd init --prefix <prefix> plus the repo scaffolding steps.brainstorming when the problem is still fuzzy or underexplored.brainstorming leaves material factual uncertainty that affects architecture, feasibility, integration points, or swarm bead quality, use planner-research before finalizing the plan.beads-planner to create or update the beads from the approved plan.validate-beads in the same planner session.validate-beads before ending the session.beads-claim, writing-plans, repo-local build-and-test, swarm-epic, or beads-close.validate-beads or why it is manual-only.