Agent skill · Workflow & Productivity

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).

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

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

Facts
Files in the skill folder: 1
SKILL.md size: 10 KB
Bundled scripts: none
Path: skills/bcc-clean-cut/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-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](../bcc-breaking-coding-chaos/references/SESSION.md) | | Chat this session | **APPROVE implement** / “开写” / explicit skip-gate | **human_APPROVE=yes** if **either**: - Chat this session clearly APPROVE impl

What's inside
Steps it walks through
  1. Workflow preflight (required — before any code edit)
  2. 1. Snapshot disk + session
  3. 2. Is bcc-clean-cut appropriate now?
  4. 3. Coding readiness checklist (all should be true, or user override)
  5. 4. After preflight OK
  6. Preconditions (short)
  7. PLAN freeze (execute, don't refine)
  8. Intensity (default full)
  9. Before the ladder
  10. The ladder (stop at first rung that holds)
  11. Rules
  12. Never simplify away
  13. Verify + PLAN 约减 (progress only)
  14. Output
More from breaking-coding-chaos
All skills →
About this skill
What does the bcc-clean-cut skill do?

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).

How do I install it?

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