メニュー
Create beads from a spec (full decomposition) or from user input (ad-hoc issues). Single entry point for all bead creation.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Enforces staged execution discipline on large tasks: a written stage plan, parallel delegation where the runtime supports it, a failable verification check at each stage, and a skeptical self-review before delivery. Trigger when the user explicitly asks ("do this thoroughly", "be systematic", "deep work mode") OR when the task objectively spans multiple files, multiple sources, or multiple sessions. Do NOT trigger on ordinary multi-step requests that a direct attempt handles fine.
Bootstrap project orchestration with beads task tracking.
Core engineering principles for implementation tasks
Dispatch the implementation supervisor for a bead task. Resolves the correct supervisor from the assignee field, checks branch state, and dispatches with full context.
QA finalization gate — validates spec conformity, runs tests/build/lint, produces a structured QA report. Auto-dispatches the supervisor for rework on FAIL. Last gate before human merge.
Code review gate — dispatches the code-reviewer agent to analyze an implementation branch, tracks findings, and auto-dispatches the supervisor for rework when verdict is NEEDS-REWORK.
| name | tasks |
| description | Create beads from a spec (full decomposition) or from user input (ad-hoc issues). Single entry point for all bead creation. |
| user_invocable | true |
Create epics and issues — either by decomposing a spec or from ad-hoc user input.
Determine the mode:
Ad-hoc mode:
Dispatch using exactly these parameters — no more, no less:
Agent(
subagent_type="beads-owner",
prompt="Create epics and issues for the requested solution. Product requirements: {prd_path}. Spec: {spec_path}. Read both documents for full context before creating issues. CRITICAL — Reference-only beads: set --spec-id to the PRD document reference. Set --external-ref to the spec path with section references. Set --design to a one-line pointer (e.g., 'See {spec_path} § {section}'). Acceptance criteria must be verifiable pass/fail conditions only — no implementation details. NEVER copy spec content into description or design fields. Tasks define WHAT to do; specs define HOW to do it. Beads track work; specs define work."
)
Do NOT add extra parameters unless the user explicitly requests it.
Gather context:
Dispatch using exactly these parameters — no more, no less:
Agent(
subagent_type="beads-owner",
prompt="Create issues based on the following context. Issue description: {user_input_or_summary}. Reference documents: {doc_paths_if_any}. Parent epic: {epic_id_or_none}. Project type: {monorepo with package X | single-repo}."
)
Do NOT add extra parameters unless the user explicitly requests it.
1. Verify epics and issues were created 2. Show the user a summary: number of epics, total issues, dependency graph Stage 2 complete. Recommend proceeding to Stage 3: Guided: `/implementation {NN}` — walks through investigate → do → review → quality per task Direct: `/investigate` — jump straight to investigating a taskUse bd ready to see available work.