القائمة
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.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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.
| name | autoloop |
| description | 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. |
| when_to_use | Use only after a reviewed plan exists and the user explicitly asks for /autoloop. Do not use for idea shaping, plan creation, destructive operations, vague "keep going" requests, or simple one-off changes. |
| argument-hint | [plan] |
| user-invocable | true |
| allowed-tools | ["Bash","Read"] |
If builder says 别走流程, 直接做, 简单点, or 不走地图, do not run /autoloop. Acknowledge once and do the smallest direct action.
Exception: the escape hatch does not bypass safety gates for destructive changes, secret access, public upload, deploy, database migration, force push, or irreversible writes.
/autoloop is an explicit automation wrapper for mature, already-approved plans.
It may run:
/execute -> /verify -> /ship
It must not create a plan, expand scope, choose new dependencies, perform destructive actions, push, open a PR, or publish unless the active plan and /ship both say that action is in scope and builder explicitly approves it.
Before doing anything else:
bash ${BDC_HOME:-$HOME/.bdc}/scripts/active-plan-resolver.sh --single
If any precondition fails, stop and report the exact missing condition. Do not downgrade into ad-hoc /execute.
/execute on the next unchecked step./execute passes, run /verify on the finished work./verify returns APPROVE, continue until the next boundary or until no unchecked steps remain./verify returns REQUEST_CHANGES, treat it as failure 1 and run one correction loop through /execute./handoff./ship for local-first go/no-go. Do not push, publish, or open a PR unless /ship asks for it and builder confirms.| Event | Count |
|---|---|
/execute verify failure | 1 |
/verify REQUEST_CHANGES | 1 |
/ship NO-GO with actionable fix | 1 |
| Same stage fails again after one correction loop | stop |
Two accumulated failures in one /autoloop invocation require:
/handoff or write the equivalent handoff if the handoff skill is unavailable/autoloop. Because: automation must not hide irreversible decisions./autoloop is a local execution wrapper, not a release authority./execute scope checks define the atomic boundary./autoloop starts after planning is frozen.Keep a compact running ledger:
Autoloop:
- Plan: <path>
- Current stage: execute | verify | ship | stopped
- Passed: <count>
- Failures: <count>/2
- Last evidence: <command or verdict>
- Next action: <continue | stop | handoff | ship>
active-plan-resolver.sh --single./execute produced fresh verify evidence before /verify./verify returned APPROVE before /ship./ship produced GO/NO-GO and rollback/restore notes before any release action./autoloop starts from a fuzzy idea or unreviewed plan.REQUEST_CHANGES as a warning instead of a failure.| Rationalization | Response |
|---|---|
| "The plan is probably approved because it exists." | Do not assume. Incident: standards/debugging.md 2026-04-04 records written rules being ignored until hard gates enforced them; approval must be explicit. |
| "One more retry might fix it." | Stop after the budget. Incident: large health baseline runs require durable handoff state instead of unbounded continuation. |
${BDC_HOME:-$HOME/.bdc}/standards/roadmap.md${BDC_HOME:-$HOME/.bdc}/skills/execute/SKILL.md${BDC_HOME:-$HOME/.bdc}/skills/verify/SKILL.md${BDC_HOME:-$HOME/.bdc}/skills/ship/SKILL.md${BDC_HOME:-$HOME/.bdc}/skills/handoff/SKILL.md