| 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. |
using-bdc
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.
Step 0: Escape Hatch
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.
Roadmap
/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.
Route
| 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 |
Active plan check
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.
Health check
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.
Checklist references
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 |
