cc10x

Current version: 12.8.2

---

Install

Step 1 — Add the marketplace:

/plugin marketplace add romiluz13/cc10x

Step 2 — Install the plugin:

/plugin install cc10x@cc10x

Then say "set up cc10x for me" in Claude Code and restart. Done.

---

Quick Start Examples

Build Something

"build a user authentication system"

→ Router detects BUILD intent
→ Stops to resolve missing requirements first
→ component-builder drives RED → GREEN → REFACTOR
→ code-reviewer + failure-hunter run in parallel
→ integration-verifier checks wiring, artifacts, and behavior
→ Workflow state and memory are updated

Fix a Bug

"debug the payment processing error"

→ Router detects DEBUG intent
→ Loads prior failures and project memory
→ bug-investigator starts from logs and observed behavior
→ code-reviewer checks the fix path
→ integration-verifier confirms the bug is actually closed
→ Useful findings go back into memory

Review Code

"review this PR for security issues"

→ Router detects REVIEW intent
→ code-reviewer uses repo and git context
→ Reports findings only when confidence clears the bar
→ Every finding includes file:line evidence

---

Why cc10x

Ask Claude for something complex. It works for a while. Then it declares "Done!" — tests still red, refactor half-finished, and by message 40 it's contradicting itself because the context is gone.

cc10x fixes the loop, not the prompt. A better model running free loses to the same model, constrained and looped correctly. That's the whole bet.

The pain you know	How cc10x handles it
"Done!" on red tests	integration-verifier is independent of the builder. Phase-exit gates block advancement on partial evidence.
Silent failures nobody asked about	failure-hunter runs in parallel with review — greps for swallowed errors and empty catches.
Context falls apart after compaction	Workflow state on disk with stable UUIDs. Memory files the router auto-heals.
Planning is just a chat	Three planning modes chosen by intent, with a fresh anti-anchored review by a reviewer who never saw the planner's rationale.
12 slash commands to remember	One router. Every request hits cc10x-router first.
.claude/ prompt spam on every fanout	State lives at .cc10x/ — outside .claude/, so the harness's sensitive-file gate never fires.
Green tests that prove nothing	Test Honesty Gates grep for getByTestId('…-mock'), as any, .find() bypass, setTimeout() waits. A hit can't count as PASS on that test's strength alone.
Reviewer findings that sound right but aren't	Every finding at confidence ≥80 needs a verbatim file:line quote or it's auto-demoted. The verifier independently re-reads the line and drops hallucinated findings before they can gate.
Orchestrator context rotting with pasted history	Dispatch by reference, not by blob — the diff is written to disk, the prompt passes a path, never a body. (One real dispatch hit 42k chars, 99% pasted history. The scar became law.)

---

How It Works

You describe the work. cc10x routes it, brings in the right specialists, and keeps the bar for "done" higher than a convincing paragraph.

                        YOU
                         │
                         ▼
            ┌────────────────────────┐
            │      cc10x-router      │  ◄── only entry point
            │   detects intent       │
            └────────────┬───────────┘
                         │
          ┌──────────────┼──────────────┬─────────────┐
          │              │              │             │
          ▼              ▼              ▼             ▼
        BUILD          DEBUG         REVIEW         PLAN
          │              │              │             │
          ▼              ▼              ▼             ▼
    component-      bug-          code-          planner
      builder    investigator   reviewer            │
          │              │              │             ▼
          ▼              ▼           (done)     plan-gap-
  [code-reviewer    code-reviewer             reviewer
   ∥ silent-            │
   failure-            ▼
    hunter]      integration-
          │         verifier
          ▼
   integration-
     verifier

                 ┌──────────────────────────┐
                 │  STATE (every workflow)  │
                 │  activeContext.md        │
                 │  patterns.md            │
                 │  progress.md            │
                 │  {wf}.json + .events    │
                 └──────────────────────────┘

---

Claude Setup Instructions

This section is written for Claude Code to follow when the user says "set up cc10x for me".

When user says "set up cc10x", "install cc10x", or similar:

Step 1: Check Existing Files

• Read ~/.claude/CLAUDE.md (may not exist)
• Read ~/.claude/settings.json (may not exist)

Step 2: Update ~/.claude/CLAUDE.md

If file doesn't exist: CREATE with the template below. If file exists: PREPEND the cc10x section below, keep user's existing content.

Multi-project note: The global ~/.claude/CLAUDE.md activates cc10x in every project automatically — you do not need to reinstall or reconfigure per project. Only add the cc10x section to a project's .claude/CLAUDE.md if that project has its own conflicting CLAUDE.md already.

# CC10x Orchestration (Always On)

IMPORTANT: ALWAYS invoke cc10x-router on ANY development task. First action, no exceptions.
IMPORTANT: Do only minimal orientation if needed, then invoke the router immediately.
IMPORTANT: Prefer retrieval-led reasoning over pre-training-led reasoning for orchestration decisions.
IMPORTANT: Never bypass the router. It is the system.
IMPORTANT: NEVER use Edit, Write, or Bash (for code changes) without first invoking cc10x-router.

**Skip CC10x ONLY when:**
- User EXPLICITLY says "don't use cc10x", "without cc10x", or "skip cc10x"
- No interpretation. No guessing. Only these exact opt-out phrases.

[CC10x]|entry: cc10x:cc10x-router

---

## Complementary Skills (Work Together with CC10x)

**Skills are additive, not exclusive.** CC10x provides orchestration. Domain skills provide expertise. Both work together.

**GATE:** Before writing code, check if task matches a skill below. If match, invoke it via `Skill(skill="...")`.

| When task involves... | Invoke |
|-----------------------|--------|
| *(Add user's installed skills here)* | |

Step 3: Update ~/.claude/settings.json

If file doesn't exist: CREATE with the template below. If file exists: MERGE these permissions into the existing permissions.allow array (don't overwrite!):

"Bash(mkdir -p .cc10x)",
"Bash(mkdir -p docs/plans)",
"Bash(mkdir -p docs/research)",
"Bash(mkdir -p docs/solutions)",
"Bash(git status)",
"Bash(git diff:*)",
"Bash(git log:*)",
"Bash(git branch:*)",
"Bash(git blame:*)",
"Bash(git ls-files:*)",
"Bash(git rev-parse:*)",
"Bash(python3:*)",
"Edit(.cc10x/*)",
"Write(.cc10x/*)"

Why the Edit/Write permissions? The live cc10x memory namespace is .cc10x/. The permission examples use the .cc10x/* scope so the namespace works without re-prompting on every memory write.

Why git rev-parse and python3? Every BUILD phase records its base SHA (git rev-parse HEAD), and the router produces review diff packages and phase briefs by running plugin tools via python3. Without these two, every phase prompts mid-workflow.

Step 4: Set User Standards (Optional)

Ask the user:

"Do you have coding standards or principles you want cc10x agents to always follow? (e.g. 'always use TypeScript strict mode', 'follow SOLID principles', 'never use any', 'prefer functional patterns')"

If user provides standards, write them to the project's memory:

Bash(command="mkdir -p .cc10x")
# Check if patterns.md already exists (Read returns error = doesn't exist)
Read(file_path=".cc10x/patterns.md")

# If it DOESN'T exist — create with standards already populated:
Write(file_path=".cc10x/patterns.md", content="# Project Patterns\n<!-- CC10X MEMORY CONTRACT: Do not rename headings. Used as Edit anchors. -->\n\n## User Standards\n- {standard 1}\n- {standard 2}\n\n## Common Gotchas\n\n## Project SKILL_HINTS\n\n## Last Updated\n{date}")

# If it DOES exist — append under User Standards:
Edit(file_path=".cc10x/patterns.md",
     old_string="## User Standards",
     new_string="## User Standards\n- {standard 1}\n- {standard 2}")

Read(file_path=".cc10x/patterns.md")  # Verify

If user skips: No action. The memory file will be created on first workflow run with an empty ## User Standards section for them to fill in later.

Step 5: Scan Installed Skills & Add to Table

Where to find installed skills:

1. ~/.claude/settings.json → check enabledPlugins object (plugins with value true)
2. ~/.claude/plugins/installed_plugins.json → detailed plugin info
3. ~/.claude/skills/ → personal skills (all projects)
4. .claude/skills/ → project-specific skills

Skill naming in table:

• Plugin skills: plugin-name:skill-name (e.g., mongodb-agent-skills:mongodb-schema-design)
• Personal/project skills: just the skill name (e.g., react-best-practices)

Example: If user has these:

# In enabledPlugins:
"mongodb-agent-skills@mongodb-agent-skills": true

# In ~/.claude/skills/:
react-best-practices/SKILL.md

Add to the Complementary Skills table:

| When task involves... | Invoke |
|-----------------------|--------|
| MongoDB, schema, queries | `mongodb-agent-skills:mongodb-schema-design` |
| React, Next.js, UI | `react-best-practices` |

Step 6: Confirm

"cc10x is set up! Please restart Claude Code to activate."

---

The 4 Workflows

Intent	Trigger Words	What Happens
BUILD	build, implement, create, make, write, add	Clarify scope → TDD implementation → adversarial review → integration verification
DEBUG	debug, fix, error, bug, broken, troubleshoot	Reproduce from evidence → isolate cause → validate fix → prove no regression
REVIEW	review, audit, check, analyze, assess	High-signal review with confidence thresholds and file:line citations
PLAN	plan, design, architect, roadmap, strategy	Turn rough intent into an execution-ready plan with explicit decisions

---

Memory Persistence

cc10x survives context compaction. This is critical for long sessions.