bcc-clean-cut
BCC minimal implement from locked PLAN.md (ponytail ladder + verify). Slash: /bcc-clean-cut · chat: bcc:clean-cut · "implement PLAN" after human APPROVE. Not for plan grill (use bcc-plan-spar).
bo-cao · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add bo-cao/breaking-coding-chaos --skill bcc-clean-cut技能说明
name: bcc-clean-cut description: > BCC minimal implement from locked PLAN.md (ponytail ladder + verify). Slash: /bcc-clean-cut · chat: bcc:clean-cut · "implement PLAN" after human APPROVE. Not for plan grill (use bcc-plan-spar). argument-hint: "slash: /bcc-clean-cut · chat: bcc:clean-cut · [lite|full|ultra]" metadata: short-description: "BCC minimal code from PLAN"
bcc-clean-cut
Job: ship the shortest correct code that satisfies the active PLAN.md, then verify and progress-only 约减 the checklist.
Deep source: ponytail SKILL.md (coding ladder only — not review/audit family).
Does not: interview the user for domain design, write ADRs, adversarial-review the plan, or refine PLAN design while coding — do that in bcc-plan-spar first.
Workflow preflight (required — before any code edit)
Do not write product code until this check passes.
If uncertain → ask the user (one question + recommended default). Never invent APPROVE.
1. Snapshot disk + session
| Check | Read |
|---|---|
| Global map | plans.md / progress.md (if present) — which hardpoint is current? |
| Coding brief | PLAN.md (or plan_path from session) — exists? draft? locked? checklist open items? |
| Domain | CONTEXT.md / ADRs if referenced by PLAN |
.bcc/session.json | Cross-session APPROVE — see SESSION.md |
| Chat this session | APPROVE implement / “开写” / explicit skip-gate |
human_APPROVE=yes if either:
- Chat this session clearly APPROVE implement / skip-gate, or
- Session file has
approved_for=clean-cutandplan_sha256equals SHA-256 of current PLAN file bytes.
If session says approved but hash mismatch → PLAN changed after approve → human_APPROVE=no → ask re-APPROVE or plan-spar (do not code).
Echo:
preflight · PLAN=… · human_APPROVE=yes|no|unclear · session=… · hash=match|mismatch|none · throughline=yes|no · recommend=code|plan-spar|throughline|ask-user
2. Is bcc-clean-cut appropriate now?
| Situation | Suitable? | Do this |
|---|---|---|
No PLAN.md | No | Stop. Send to bcc-plan-spar. Ask if they meant to plan first. |
PLAN.md is _Draft — not locked_ | No | Stop. Finish bcc-plan-spar lock (or ask user to force-lock). |
| Checklist all complete / slice already shipped | Usually no | Ask: “PLAN is done. New slice (plan-spar), throughline next, or re-open checklist?” |
| PLAN topic ≠ user’s request / ≠ throughline current hardpoint | Ask | “PLAN is for X; you asked to implement Y. Switch (plan-spar), or implement X?” |
Human APPROVE implement this session or valid .bcc/session.json approve (hash match) | Yes | Proceed to ladder |
| User said “implement / clean-cut” but no chat APPROVE and no valid session approve | Ask | “PLAN is locked but not human-approved for coding. APPROVE implement, amend, or back to plan-spar?” Default recommend: confirm APPROVE once. |
| User only asked “where are we?” | No | bcc-throughline |
| User still wants alignment / more grill | No | bcc-plan-spar |
| Multi-step endeavor, no throughline, large remaining work | Warn + ask | Optional: “No plans.md cockpit — continue one-off cut, or create throughline first?” Coding may proceed if PLAN is solid and user wants speed. |
3. Coding readiness checklist (all should be true, or user override)
PLAN.mdexists and is not an unlabeled draft.- Goal + checklist + verification sections are present enough to execute.
- Human has approved implement (chat or valid session file) or explicit override (“skip gate / just code this PLAN”).
- You know which slice this PLAN is for (title/goal matches the work / session.active_slice).
If any item fails and user did not override → do not code; ask or route.
4. After preflight OK
Only then: optionally set session status=coding → read code flow → ladder → verify → 约减 PLAN → throughline writeback → on pass set session status=done, approved_for=none (consume one-shot approve per SESSION.md).
Preconditions (short)
- Preflight passed (above).
- Trace the real code flow before editing.
- PLAN is the contract — no invented scope.
PLAN freeze (execute, don't refine)
After human APPROVE, PLAN.md is a frozen contract for design content.
| Allowed during cut | Forbidden during cut |
|---|---|
| Implement within Goal / Approach / checklist / Verification | Rewrite Goal, Approach, Key decisions, Out of scope, Verification design |
Check off [ ] → [x] only after implement + verify | Add new checklist items, “improve” wording of the brief, expand scope |
| 约减 progress only: remove completed checklist rows / finished bulk that is already done | Mid-cut plan polish, second-guess architecture into the file |
Note learnings in progress.md / findings.md | Quietly change the brief so APPROVE no longer matches reality |
Conflict / plan wrong / can't meet Verification: stop coding → say the conflict in one short line → bcc-plan-spar (or user amends PLAN) → re-APPROVE. Do not “fix the plan while shipping.”
No extra user ceremony: same gates as today; agent just won't rewrite the brief while coding.
Intensity (default full)
| Level | Behavior |
|---|---|
| lite | Build what PLAN asks; name a lazier alternative in one line. |
| full | Ladder enforced. Shortest correct diff. Default. |
| ultra | YAGNI extremist on the code. May mention a speculative checklist item in chat; still execute PLAN as approved unless user sends you back to plan-spar. Never edit design sections to “improve” the plan. |
Echo: bcc-clean-cut · full · PLAN.md
Off only if user says stop bcc-clean
阅读完整来源 ↗