メニュー
Use when a Claude Code session needs to route a task into builder's local BDC skills, standards, active plan flow, /execute execution loop, handoff, or PR/watch utilities, and no more specific skill has already matched.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when the user explicitly invokes /autoloop to automate an already-approved plan through /execute, /verify, and /ship with bounded retries and handoff on repeated failure.
Use when builder says 开始做 / 做吧 / 执行 / go / start / 跑起来 / 走起 / execute / execute-plan and an approved `.bdc/plans/*.md` exists; execute plan steps with verify evidence, scope checks, commits, and checkbox progress. Skip if no plan exists, pure Q&A, or a trivial one-off change.
Session wrap-up — produces a HANDOFF file at `${BDC_HOME:-$HOME/.bdc}/handoff/<topic-slug>.md` for the next session's AI. Format spec: `standards/ai-friendly-artifacts.md` § 1.4.2. Pending matters more than Done. Use when builder says handoff / 收尾 / 总结一下 / 交接 / 交代一下 / wrap up / session 结束, or PreCompact hook prompts. Skip pure Q&A, mid-execution unstable state, or if the same target handoff was already written within 5 min (per Phase 1.5 recency guard).
Use when builder invokes /health, asks to check BDC health, asks whether the installed BDC harness is stable, or asks for a no-spend local BDC verification.
Load a previous session's HANDOFF brief into context to resume work — distinct from Claude Code's `/resume` which restores the full conversation; this loads only the lightweight YAML brief emitted by /handoff. Default state at session start is clean (no auto-load). Use when builder invokes /pickup, /pickup <N>, /pickup <keyword>, or says 接上次 / 续上次 / 接活. Skip if not explicitly requested, pure Q&A, or builder already started a different task.
Use when the user explicitly invokes /ship or asks whether finished BDC, code, docs, or release work is ready to ship, publish, merge, or close out.
| name | using-bdc |
| description | Use when a Claude Code session needs to route a task into builder's local BDC skills, standards, active plan flow, /execute execution loop, handoff, or PR/watch utilities, and no more specific skill has already matched. |
Orient a fresh session to the local BDC without becoming a broad automatic hook.
Do not wire this skill into UserPromptSubmit. Because: it is an orientation skill for choosing a BDC route, not a broad automatic hook.
If builder says 别走流程, 直接做, 简单点, or 不走地图, do not route into the BDC map. Acknowledge once and do the smallest direct action.
Exception: do not bypass safety gates for destructive changes, secret access, public upload, deploy, database migration, force push, or irreversible writes.
/idea -> /plan -> /execute -> /verify -> /ship
Use ${BDC_HOME:-$HOME/.bdc}/standards/roadmap.md as the source of truth for the five-station map. /autoloop is an explicit automation wrapper, not a sixth station.
Use ${BDC_HOME:-$HOME/.bdc}/standards/route-intent.md as the source of truth for natural-language routing, escape directives, meta questions, and high-risk false-positive routes.
| User intent | Route |
|---|---|
| Clarify a fuzzy idea before planning | /idea |
| Need a written plan | plan |
| Start executing an approved plan | execute |
| Review completed work independently | /verify |
| Decide whether work is ready to ship | /ship |
| Explicitly automate an approved plan | /autoloop |
| Continue from prior work | pickup or handoff |
| Watch pull request or GitHub events | watch-pr |
| Graph or query local knowledge | Out of BDC core |
| Check BDC health | /health or ${BDC_HOME:-$HOME/.bdc}/bin/bdc doctor |
| Need standards map | ${BDC_HOME:-$HOME/.bdc}/standards/dispatch.md |
If the user says "start", "开始", "go", or "执行", first check whether an active plan exists:
bash ${BDC_HOME:-$HOME/.bdc}/scripts/active-plan-resolver.sh --list
If exactly one active plan is selected, route to /execute. If multiple filesystem candidates appear, first resolve from current-session evidence: explicit plan path/name in the prompt, the plan just created/reviewed/approved in this session, a current-plan cursor if present, current repo target root, or a clear project/topic match. If one candidate is uniquely supported, route to /execute and state the reason. Do not ask builder solely because the resolver returned multiple stale active plans; ask only when no unique candidate remains after context resolution, or when the next action is destructive/irreversible.
Before or after BDC self-modification, run:
${BDC_HOME:-$HOME/.bdc}/bin/bdc doctor
Use framework-health.sh as a narrower framework-rule self-check when the task is about plans, hooks, or rule lint specifically. Use /health for overall BDC health.
Load checklist references on demand, not always-on:
| Situation | Reference |
|---|---|
| test design / assertions / E2E patterns | ${BDC_HOME:-$HOME/.bdc}/standards/checklists/testing-patterns.md |
| auth / secrets / input validation / dependency risk | ${BDC_HOME:-$HOME/.bdc}/standards/checklists/security.md |
| web or backend performance risk | ${BDC_HOME:-$HOME/.bdc}/standards/checklists/performance.md |
| UI accessibility | ${BDC_HOME:-$HOME/.bdc}/standards/checklists/accessibility.md |
| fan-out, subagent, or command orchestration | ${BDC_HOME:-$HOME/.bdc}/standards/checklists/orchestration.md |
| migrations / deprecations / simplification / ADRs | ${BDC_HOME:-$HOME/.bdc}/standards/checklists/harness-local-rules.md |