菜单
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.
用 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).
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.
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.
| name | health |
| description | 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. |
| when_to_use | Use for BDC health checks. Do not use for normal project tests, GitHub CI, or application-specific build failures unless the question is about the BDC itself. |
| argument-hint | [--quick|--baseline] |
| user-invocable | true |
| disable-model-invocation | true |
| allowed-tools | ["Bash"] |
Run the executable health checker. Do not judge BDC health from memory.
/health is the only user-facing BDC health entrypoint. It runs local deterministic checks by default.
If builder invokes /health with no argument, run:
bash ${BDC_HOME:-$HOME/.bdc}/scripts/hook-health-check.sh
Report:
| Argument | Action |
|---|---|
--quick | Run hook-health-check.sh. Local only, no remote spend and no paid model calls. |
--baseline | Run local deterministic checks when the source repo is available, otherwise run hook-health-check.sh. Local only, no remote spend and no paid model calls. |
/health --quick must run hook-health-check.sh./health --baseline must run local-only baseline checks when the source repo is available.| Rationalization | Response |
|---|---|
| "The last release gate was green, so current health is green." | Do not collapse the facts. Run the current health command and report fresh evidence. |
| "Just run every possible check to be sure." | Do not from a vague health request. /health --quick is the default no-spend gate; use /health --baseline only when a broader local check is requested. |