bcc-breaking-coding-chaos
BCC main skill: dual-loop coding workflow (throughline → plan-spar → clean-cut) or quick status+next. Slash: /bcc-breaking-coding-chaos · chat: bcc:breaking-coding-chaos · "run BCC" · "BCC status" · "what next BCC". Needs a real idea (1:1 implement).
Profile →npx skills add bo-cao/breaking-coding-chaos --skill bcc-breaking-coding-chaos --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# bcc-breaking-coding-chaos **One main skill + three sub-skills.** This file is the only “big” entry; the three children own deep rules. | Sub-skill | Role | |-----------|------| | [bcc-throughline](../bcc-throughline/SKILL.md) | Global map: `plans.md` / `progress.md` / `findings.md` only | | [bcc-plan-spar](../bcc-plan-spar/SKILL.md) | After throughline: single `PLAN.md` align + review | | [bcc-clean-cut](../bcc-clean-cut/SKILL.md) | After human APPROVE: minimal code + verify + writeback | Internal notes (not separate slash skills): [references/SESSION.md](./references/SESSION.md), [references/WRITEBACK.md](./references/WRITEBACK.md). **Prerequisite:** a **reasonably concrete idea**. BCC is **1:1 implement + control**, not ideation from zero. --- ## Shared voice (Mode A and Mode B) Talk like a sharp collaborator on **their work** — not a workflow product or ceremony host. | Do | Don't | |----|--------| | Lead with goal / map / next choice | “先对齐上下文 / BCC 双环说明 / 恢复账本” on cold start | | Short human gates (confirm hardpoint, APPROVE implement) | Unprompted “还没写代码 / throughline 不写产品代码” lectures | | Load each child skill and follow **its** voice rules | Dump file-role tables, 5-questio
- Shared voice (Mode A and Mode B)
- Two modes (this skill)
- Mode A — full chain
- Mode B — user drives
- Quick status (built-in — not a separate skill)
- Hard workflow rules (remind only)
- What NOT to do
What does the bcc-breaking-coding-chaos skill do?
BCC main skill: dual-loop coding workflow (throughline → plan-spar → clean-cut) or quick status+next. Slash: /bcc-breaking-coding-chaos · chat: bcc:breaking-coding-chaos · "run BCC" · "BCC status" · "what next BCC". Needs a real idea (1:1 implement).
How do I install it?
Run `npx skills add bo-cao/breaking-coding-chaos --skill bcc-breaking-coding-chaos --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From bo-cao/breaking-coding-chaos, a repository with 13 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.