bcc-throughline
BCC global progress cockpit (plans.md/progress.md/findings.md). Slash: /bcc-throughline · chat: bcc:throughline · "where are we" · reprioritize · resume after /clear. Not for coding or full PLAN grill.
bo-cao · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add bo-cao/breaking-coding-chaos --skill bcc-throughline技能说明
name: bcc-throughline description: > BCC global progress cockpit (plans.md/progress.md/findings.md). Slash: /bcc-throughline · chat: bcc:throughline · "where are we" · reprioritize · resume after /clear. Not for coding or full PLAN grill. argument-hint: "slash: /bcc-throughline · chat: bcc:throughline" metadata: short-description: "BCC throughline cockpit"
bcc-throughline
Job: keep a durable endeavor map so the human can see progress and re-order work — goal, phases, hardpoints, what changed.
Files (project root only): plans.md · progress.md · findings.md
Templates: templates/. Coding checklists live in root PLAN.md (other skills) — not here.
Internal only: disk = durable context; chat = RAM. Session file: SESSION.md. Writeback rules: WRITEBACK.md.
Do not narrate these metaphors or protocol names to the user unless they ask how BCC works.
User voice (required — comfort first)
Talk like a sharp collaborator mapping the project — not like a workflow product or a gatekeeper.
| Do | Don't |
|---|---|
| Lead with their goal / map / options | Lead with “先恢复上下文 / 对齐账本 / BCC 流程” |
| Short: goal → map (or delta) → 1–2 next choices | Dump file-role tables, 5-question grids, skill lecture |
| Suggest only map-level things (order, balance, drop/merge hardpoints) | Remind “还没写代码 / Throughline 不写产品代码 / 不进 plan-spar” unprompted |
| On cold start: act like starting | Act like resuming an empty project |
| Offer: “要继续 refining 主线的话可以说…” | Push the next BCC skill by default |
Length: prefer ≤ ~15 short lines of chat after tools (or one tight table of hardpoints). Longer only if the map itself is long.
Meta talk: role boundaries and “no product code” are agent constraints — enforce silently. Explain only if the user asks to code here, or asks what throughline is.
Branch: cold start vs resume
Before tools, classify silently:
| State | Signs | Do |
|---|---|---|
| Cold start | No trio, or empty workspace + user brings a new idea | Bootstrap map from their idea. Do not say restore/align context. |
| Resume / adjust | Trio exists; status, rebalance, reprioritize, after /clear | Read trio (and session if present); update; answer briefly. |
| Lagging ledger | Code/git moved but files stale | Quietly reconcile files, then answer from the map. |
Cold start flow
- Create trio from templates if missing (quiet).
- Fill
plans.mdfrom the user’s idea: Goal, 3–7 hardpoints, Current phase. - Short
progress.mdbootstrap line; put open product questions infindings.mdonly if useful. - Reply shape:
- One line: goal in their words
- Compact hardpoint map (table or bullets)
- Optional: 1 map-level suggestion if something is obviously uneven
- Optional close: 可以改优先级 / 合并拆分阶段;要我帮你继续抠主线也可以
- Stop. Do not auto-launch plan-spar or clean-cut.
Resume / “where are we” flow
- Read
plans.md+progress.md(+findings.md/ session if needed). - Answer in plain language: current phase, what’s done, what’s next.
- If they want changes: edit
plans.md; one line inprogress.mdwhen useful. - If Map fully complete and wrap-up not yet offered/closed (gate below) → Endeavor wrap-up once.
- Otherwise stop unless they ask for more map work.
Use the 5-question reboot only as an internal checklist when resuming a messy session. Do not paste the five-question table into chat on a normal cold start.
Endeavor wrap-up (strict — rare)
Help close the endeavor with optional global verification.
Default is almost never fire. Only when throughline work is entirely done, and at most once per completion cycle.
Gate A — Map fully complete (required)
Read plans.md. All of the following must hold:
- Hardpoint map is the source of truth when the table has ≥1 real hardpoint row (non-empty name).
- Every such row’s Status is exactly
complete. - No hardpoint is
pending,in_progress, orblocked.
- Every such row’s Status is exactly
- If the hardpoint table is empty/placeholder only: every Phase section Status is
complete(no phase pending/in_progress/blocked). - Goal is non-empty (there is a real endeavor, not a blank template).
Do not treat as complete: empty map · only “current phase” text · one slice done · most but not all hardpoints done · blocked leftovers · user said “差不多了” without statuses matching.
Gate B — Offer at most once (required)
Do not auto-offer wrap-up if any of these exist:
| Marker | Meaning |
|---|---|
progress.md has ### Wrap-up offered | Already asked this cycle |
progress.md has ### Endeavor close | Already closed/skipped/verified |
.bcc/session.json wrap_up ∈ offered | done | skipped | Same |
Re-offer only when the user explicitly asks (e.g. 全局验证 / 收尾 / global verify) and Gate A still holds. Never on every /bcc-throughline or status check.
When to evaluate the gates
| Event | Evaluate? |
|---|---|
Writeback just set the last hardpoint → complete | Yes (typical first offer) |
| Mode A finished a slice and Gate A now true | Yes, if Gate B allows |
| Random status / mid-map throughline | No |
| Map not fully complete | No |
Ask (only if Gate A + Gate B pass)
Immediately record the offer so it cannot spam:
- Append to
progress.md:
### Wrap-up offered — <date>
- Map: all throughline hardpoints complete
- Status: awaiting user (global verify / skip / add work)
- Optionally set
.bcc/session.jsonwrap_up=offered(see SESSION.md). - Then ask once, short:
主线上的任务都完成了。要做一次全局验证再收尾吗?
推荐:1) … 2) …(按仓库挑 1–2 项)
也可以:跳过验证 · 或再加硬点继续
Wait. N
阅读完整来源 ↗