bcc-plan-spar
BCC align+lock+review PLAN.md for one slice (no product code). Slash: /bcc-plan-spar · chat: bcc:plan-spar · "lock PLAN" · spar the plan. Args: rounds=N (auto-review cap), review=self|subagent|cli|auto|off. Grill until clear enough (no default Q&A quota). Hand off to bcc-clean-cut after human APPROVE.
bo-cao · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add bo-cao/breaking-coding-chaos --skill bcc-plan-spar技能说明
name: bcc-plan-spar description: > BCC align+lock+review PLAN.md for one slice (no product code). Slash: /bcc-plan-spar · chat: bcc:plan-spar · "lock PLAN" · spar the plan. Args: rounds=N (auto-review cap), review=self|subagent|cli|auto|off. Grill until clear enough (no default Q&A quota). Hand off to bcc-clean-cut after human APPROVE. argument-hint: "slash: /bcc-plan-spar · chat: bcc:plan-spar · [topic] [rounds=N] [review=…]" metadata: short-description: "BCC plan align + review"
bcc-plan-spar
Job: solid coding contract for one slice —
- Human grill (Q&A until clear enough — no default turn quota) → clear sub-plan intent
- Lock
PLAN.md(+CONTEXT/ ADRs) - Auto review (
rounds= review budget, multi-backend) → live results → main agent iterates PLAN - Human final gate → APPROVE / amend / stop
- Hand off to
bcc-clean-cut(implement — not this skill)
Deep source: grill-with-docs Act 1 (grill + domain) + Act 2 (bounded review, CLI fallback).
Formats: CONTEXT-FORMAT.md, ADR-FORMAT.md, PLAN-FORMAT.md.
Workflow preflight (required — before Phase 0/1)
Do not start grilling or rewriting PLAN.md until this check runs.
If anything is ambiguous → ask the user one clear question (with a recommended answer). Do not invent workflow state.
1. Snapshot disk (read if present)
| Path | Ask |
|---|---|
plans.md / progress.md / findings.md | Is there a global endeavor map? Where are we? |
PLAN.md | Is there an active coding brief? Draft or locked? Which slice? |
CONTEXT.md / docs/adr/* | Domain language already started? |
.bcc/session.json | Active slice / prior approve (see SESSION.md) |
| Chat this session | Did user already APPROVE implement / skip align? |
Echo a one-line status, e.g.:
preflight · throughline=yes|no · PLAN=missing|draft|locked|stale? · slice=? · session=… · recommend=grill|reuse-PLAN|hand-off-clean-cut|ask-user
2. Hard rule: throughline before plan-spar
| Check | Required |
|---|---|
plans.md exists with a non-empty Goal (and preferably a hardpoint map) | Yes |
If missing or empty:
- Do not start Phase 1 grill for a multi-step endeavor.
- Tell user: “bcc-plan-spar runs only after throughline. Run
/bcc-throughlinefirst (or Mode A/bcc-breaking-coding-chaos).” - Offer to load bcc-throughline now.
Exception: user explicitly says one-off micro task and refuses a cockpit — then ask once to confirm; if they insist, proceed but still create a minimal plans.md Goal line when possible (preferred) rather than silent skip.
3. Is bcc-plan-spar the right skill right now?
| Situation | Suitable? | Do this |
|---|---|---|
No usable throughline (plans.md) | No | bcc-throughline first (hard rule above) |
| User wants status / reprioritize only | No | bcc-throughline or main skill status |
| User wants code now and PLAN locked + APPROVED | No | bcc-clean-cut |
| User wants code now but PLAN missing / draft | Yes | Align/lock here (after throughline OK) |
| User names a hardpoint on the map | Yes | Proceed; update single root PLAN.md in place for that work |
Existing PLAN.md is for previous work | Yes | Overwrite/refresh PLAN.md for the new hardpoint (global history stays in throughline trio — not in PLAN) |
| Trivial one-liner / pure discussion | Usually no | Skip or ask |
No formal state machine. Infer from docs + chat; suggest next step if wrong skill.
4. Ask the user when uncertain
One question + recommended default:
- Throughline missing — create now?
- Which hardpoint on the map?
- Refresh
PLAN.mdfor this hardpoint (yes)? - Align vs code (plan-spar vs clean-cut)?
5. After preflight OK → Phase 0
Only then: scope hardpoint, then Phase 1 grill / lock.
Tunables
Parse from invocation (e.g. /bcc-plan-spar auth rounds=3 review=auto):
| Arg | Default | Meaning |
|---|---|---|
rounds / MAX_REVIEW_ROUNDS | 3 | Only budgeted loop: auto-review rounds after PLAN is locked. Set at spar start. 0 = skip auto review (human gate still required). |
review | auto when rounds>0, else off | Review backend (see below) |
PLAN_FILE | PLAN.md | Coding brief path |
LOG_FILE | PLAN-REVIEW-LOG.md | Append-only live review transcript |
Not a tunable by default: Phase 1 human Q&A has no default turn quota. Grill until the agent judges clear enough (or the human locks / stops).
Optional override only if the user explicitly passes grill_rounds=N / MAX_GRILL_ROUNDS=N — treat as a soft safety ceiling, not a target to fill. Do not invent or announce a default grill cap.
review modes (simplified)
| Mode | Who reviews | When to use |
|---|---|---|
auto | subagent if spawn works; else self. If user set review=cli and a CLI exists, may use CLI | Default |
subagent | Fresh reviewer subagent (read-only) — preferred isolation | Stronger critique vs builder |
self | Same agent, critic stance only | Always available 保底 |
cli | Optional local CLI (e.g. codex exec -s read-only if installed) | User opts in; fallback to self on failure |
off | Skip auto review | Human gate only after lock |
Do not require multi-agent products or cross-org setups. One host + optional subagent/CLI is enough.
Echo once before Act 1 (grill has no round count):
bcc-plan-spar · topic=… · review_rounds=3 · review=auto · PLAN_FILE=PLAN.md · LOG_FILE=PLAN-REVIEW-LOG.md
Flow (fixed order)
Preflight Workflow fitness (throughline? PLAN? right skill?) — ask if unsure
Phase 0 Scope slice (+ read thro
阅读完整来源 ↗