メニュー
Validate a planned epic before autonomous execution. Use after beads-planner and before swarm-epic to check dependency quality, bead size, file scope, verification instructions, and parallel-safety notes.
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 | validate-beads |
| description | Validate a planned epic before autonomous execution. Use after beads-planner and before swarm-epic to check dependency quality, bead size, file scope, verification instructions, and parallel-safety notes. |
Run a pre-execution quality gate for an epic before autonomous execution starts.
Catch planning defects before workers start coding. This is a planner-side validation pass, not an implementation step.
bd init --prefix <prefix> plus the repo scaffolding steps.bd show <epic-id> --json plus the current planning context and .beads/ state as needed.build-and-test bead when runtime behavior changedFiles:Verify:Risk:Parallel:Escalate:swarm-epicswarm-epicFiles or Verify.