Agent skill · Code Review & Quality

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.

cao bo 13★ · 1 repos on radarProfile →
claude-codecursorcodexMIT
Install
npx skills add bo-cao/breaking-coding-chaos --skill bcc-plan-spar --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 4
SKILL.md size: 18 KB
Bundled scripts: none
Path: skills/bcc-plan-spar/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 13
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# bcc-plan-spar **Job:** solid coding contract for one slice — 1. **Human grill** (Q&A until **clear enough** — no default turn quota) → clear sub-plan intent 2. **Lock** `PLAN.md` (+ `CONTEXT` / ADRs) 3. **Auto review** (**`rounds`** = review budget, multi-backend) → live results → main agent **iterates PLAN** 4. **Human final gate** → APPROVE / amend / stop 5. 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](./CONTEXT-FORMAT.md), [ADR-FORMAT.md](./ADR-FORMAT.md), [PLAN-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 al

What's inside
Steps it walks through
  1. Workflow preflight (required — before Phase 0/1)
  2. 1. Snapshot disk (read if present)
  3. 2. Hard rule: throughline before plan-spar
  4. 3. Is bcc-plan-spar the right skill right now?
  5. 4. Ask the user when uncertain
  6. 5. After preflight OK → Phase 0
  7. Tunables
  8. review modes (simplified)
  9. Flow (fixed order)
  10. Artifact separation
  11. Phase 0 — Scope
  12. Phase 1 — Human grill + lock PLAN (grill-with-docs Act 1)
  13. Purpose
  14. Interview rules
Ships with 3 files
  • ADR-FORMAT.md
  • CONTEXT-FORMAT.md
  • PLAN-FORMAT.md
More from breaking-coding-chaos
All skills →
About this skill
What does the bcc-plan-spar skill do?

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.

How do I install it?

Run `npx skills add bo-cao/breaking-coding-chaos --skill bcc-plan-spar --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.

Keep going