builders-dont-cry

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.

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.

Use when the user explicitly invokes /verify or asks for an independent review of completed plan work, diff evidence, or a finished BDC change before shipping.

Manage the v7 PR-watch daemon for the user — start/stop watching specific PRs, list current dashboard, force-resume an ignored PR. The PostToolUse hook auto-registers any PR after `git push` / `gh pr create`, so this skill is for on-demand operations, not for starting the auto chain. Use when builder says /watch-pr / 盯一下

Use when the user explicitly invokes /idea or asks to clarify a fuzzy product, workflow, BDC, or engineering idea before planning; produce a short idea brief without entering implementation.

Persist a structured exec-plan with prior-art check, atomic role-tagged steps, and blocking reviewer sign-off, written to `.bdc/plans/<proj>-<MMDD>-<topic>.md`. Use only when explicitly invoked as `/plan` or when builder names the skill by name (`plan`, `走 plan`). Do not auto-trigger from planning discussion (`做计划`, `plan 一下`) — empirical eval (Haiku 4.5 + Opus 4.7, both 0/3) showed description-level triggering is unreliable for this skill; manual gate is intentional.

Use when a session is about to say DONE, 完成, ready to push, fixed, or ✅ outside an active /execute execution loop, and the same response does not already include fresh verify output with exit code and last 5 lines.