![\"CC10x](\"assets/logo.png\"){kind=logo}
\n\n \n
\n Stop chasing better models. Engineer the loop.\n
\n\n\n Same model. Same Claude Code. Different outcome.
\n The agent forgets between turns. The harness remembers across runs.
\n cc10x writes every workflow to disk — intent, evidence, verdicts, failures — so resume, review, and verification read from the artifact, not from a context window that's already gone.\n
\n 1 router · 11 specialist agents · 20 skills · 4 workflows\n
\n\n\n Fail-closed gates · survives compaction · dispatch-by-reference · test honesty gates · anti-anchored review\n
\n\n\n Explore interactively: cc10x Explorer · Architecture Explorer\n
\n\n**Current version:** 12.8.0\n\n---\n\n## Install\n\n**Step 1 — Add the marketplace:**\n\n```bash\n/plugin marketplace add romiluz13/cc10x\n```\n\n**Step 2 — Install the plugin:**\n\n```bash\n/plugin install cc10x@cc10x\n```\n\nThen say **\"set up cc10x for me\"** in Claude Code and restart. Done.\n\n---\n\n## Quick Start Examples\n\n### Build Something\n\n```\n\"build a user authentication system\"\n\n→ Router detects BUILD intent\n→ Stops to resolve missing requirements first\n→ component-builder drives RED → GREEN → REFACTOR\n→ code-reviewer + failure-hunter run in parallel\n→ integration-verifier checks wiring, artifacts, and behavior\n→ Workflow state and memory are updated\n```\n\n### Fix a Bug\n\n```\n\"debug the payment processing error\"\n\n→ Router detects DEBUG intent\n→ Loads prior failures and project memory\n→ bug-investigator starts from logs and observed behavior\n→ code-reviewer checks the fix path\n→ integration-verifier confirms the bug is actually closed\n→ Useful findings go back into memory\n```\n\n### Review Code\n\n```\n\"review this PR for security issues\"\n\n→ Router detects REVIEW intent\n→ code-reviewer uses repo and git context\n→ Reports findings only when confidence clears the bar\n→ Every finding includes file:line evidence\n```\n\n---\n\n## Why cc10x\n\nAsk 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.\n\n**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.\n\n| The pain you know | How cc10x handles it |\n| --- | --- |\n| \"Done!\" on red tests | `integration-verifier` is independent of the builder. Phase-exit gates block advancement on partial evidence. |\n| Silent failures nobody asked about | `failure-hunter` runs in parallel with review — greps for swallowed errors and empty catches. |\n| Context falls apart after compaction | Workflow state on disk with stable UUIDs. Memory files the router auto-heals. |\n| 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. |\n| 12 slash commands to remember | One router. Every request hits `cc10x-router` first. |\n| `.claude/` prompt spam on every fanout | State lives at `.cc10x/` — outside `.claude/`, so the harness's sensitive-file gate never fires. |\n| 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. |\n| 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. |\n| 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.) |\n\n---\n\n## How It Works\n\n**You describe the work. cc10x routes it, brings in the right specialists, and keeps the bar for \"done\" higher than a convincing paragraph.**\n\n```\n YOU\n │\n ▼\n ┌────────────────────────┐\n │ cc10x-router │ ◄── only entry point\n │ detects intent │\n └────────────┬───────────┘\n │\n ┌──────────────┼──────────────┬─────────────┐\n │ │ │ │\n ▼ ▼ ▼ ▼\n BUILD DEBUG REVIEW PLAN\n │ │ │ │\n ▼ ▼ ▼ ▼\n component- bug- code- planner\n builder investigator reviewer │\n │ │ │ ▼\n ▼ ▼ (done) plan-gap-\n [code-reviewer code-reviewer reviewer\n ∥ silent- │\n failure- ▼\n hunter] integration-\n │ verifier\n ▼\n integration-\n verifier\n\n ┌──────────────────────────┐\n │ STATE (every workflow) │\n │ activeContext.md │\n │ patterns.md │\n │ progress.md │\n │ {wf}.json + .events │\n └──────────────────────────┘\n```\n\n---\n\n## Claude Setup Instructions\n\nThis section is written for Claude Code to follow when the user says \"set up cc10x for me\".\n\n**When user says \"set up cc10x\", \"install cc10x\", or similar:**\n\n### Step 1: Check Existing Files\n\n- Read `~/.claude/CLAUDE.md` (may not exist)\n- Read `~/.claude/settings.json` (may not exist)\n\n### Step 2: Update `~/.claude/CLAUDE.md`\n\n**If file doesn't exist:** CREATE with the template below.\n**If file exists:** PREPEND the cc10x section below, keep user's existing content.\n\n> **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.\n\n```markdown\n# CC10x Orchestration (Always On)\n\nIMPORTANT: ALWAYS invoke cc10x-router on ANY development task. First action, no exceptions.\nIMPORTANT: Do only minimal orientation if needed, then invoke the router immediately.\nIMPORTANT: Prefer retrieval-led reasoning over pre-training-led reasoning for orchestration decisions.\nIMPORTANT: Never bypass the router. It is the system.\nIMPORTANT: NEVER use Edit, Write, or Bash (for code changes) without first invoking cc10x-router.\n\n**Skip CC10x ONLY when:**\n- User EXPLICITLY says \"don't use cc10x\", \"without cc10x\", or \"skip cc10x\"\n- No interpretation. No guessing. Only these exact opt-out phrases.\n\n[CC10x]|entry: cc10x:cc10x-router\n\n---\n\n## Complementary Skills (Work Together with CC10x)\n\n**Skills are additive, not exclusive.** CC10x provides orchestration. Domain skills provide expertise. Both work together.\n\n**GATE:** Before writing code, check if task matches a skill below. If match, invoke it via `Skill(skill=\"...\")`.\n\n| When task involves... | Invoke |\n|-----------------------|--------|\n| *(Add user's installed skills here)* | |\n```\n\n### Step 3: Update `~/.claude/settings.json`\n\n**If file doesn't exist:** CREATE with the template below.\n**If file exists:** MERGE these permissions into the existing `permissions.allow` array (don't overwrite!):\n\n```json\n\"Bash(mkdir -p .cc10x)\",\n\"Bash(mkdir -p docs/plans)\",\n\"Bash(mkdir -p docs/research)\",\n\"Bash(mkdir -p docs/solutions)\",\n\"Bash(git status)\",\n\"Bash(git diff:*)\",\n\"Bash(git log:*)\",\n\"Bash(git branch:*)\",\n\"Bash(git blame:*)\",\n\"Bash(git ls-files:*)\",\n\"Bash(git rev-parse:*)\",\n\"Bash(python3:*)\",\n\"Edit(.cc10x/*)\",\n\"Write(.cc10x/*)\"\n```\n\n> **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.\n\n> **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.\n\n### Step 4: Set User Standards (Optional)\n\nAsk the user:\n> \"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')\"\n\n**If user provides standards**, write them to the project's memory:\n\n```\nBash(command=\"mkdir -p .cc10x\")\n# Check if patterns.md already exists (Read returns error = doesn't exist)\nRead(file_path=\".cc10x/patterns.md\")\n\n# If it DOESN'T exist — create with standards already populated:\nWrite(file_path=\".cc10x/patterns.md\", content=\"# Project Patterns\\n\\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}\")\n\n# If it DOES exist — append under User Standards:\nEdit(file_path=\".cc10x/patterns.md\",\n old_string=\"## User Standards\",\n new_string=\"## User Standards\\n- {standard 1}\\n- {standard 2}\")\n\nRead(file_path=\".cc10x/patterns.md\") # Verify\n```\n\n**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.\n\n### Step 5: Scan Installed Skills & Add to Table\n\n**Where to find installed skills:**\n\n1. `~/.claude/settings.json` → check `enabledPlugins` object (plugins with value `true`)\n2. `~/.claude/plugins/installed_plugins.json` → detailed plugin info\n3. `~/.claude/skills/` → personal skills (all projects)\n4. `.claude/skills/` → project-specific skills\n\n**Skill naming in table:**\n\n- **Plugin skills:** `plugin-name:skill-name` (e.g., `mongodb-agent-skills:mongodb-schema-design`)\n- **Personal/project skills:** just the skill name (e.g., `react-best-practices`)\n\n**Example:** If user has these:\n\n```\n# In enabledPlugins:\n\"mongodb-agent-skills@mongodb-agent-skills\": true\n\n# In ~/.claude/skills/:\nreact-best-practices/SKILL.md\n```\n\n**Add to the Complementary Skills table:**\n\n```markdown\n| When task involves... | Invoke |\n|-----------------------|--------|\n| MongoDB, schema, queries | `mongodb-agent-skills:mongodb-schema-design` |\n| React, Next.js, UI | `react-best-practices` |\n```\n\n### Step 6: Confirm\n>\n> \"cc10x is set up! Please restart Claude Code to activate.\"\n\n---\n\n## The 4 Workflows\n\n| Intent | Trigger Words | What Happens |\n| -------- | --------------- | -------------- |\n| **BUILD** | build, implement, create, make, write, add | Clarify scope → TDD implementation → adversarial review → integration verification |\n| **DEBUG** | debug, fix, error, bug, broken, troubleshoot | Reproduce from evidence → isolate cause → validate fix → prove no regression |\n| **REVIEW** | review, audit, check, analyze, assess | High-signal review with confidence thresholds and file:line citations |\n| **PLAN** | plan, design, architect, roadmap, strategy | Turn rough intent into an execution-ready plan with explicit decisions |\n\n---\n\n## Memory Persistence\n\ncc10x survives context compaction. This is critical for long sessions.\n\n```\n.cc10x/\n├── activeContext.md # What you're working on NOW\n│ - Current task\n│ - Active decisions (and WHY)\n│ - Learnings this session\n│\n├── patterns.md # Project conventions\n│ - Code patterns\n│ - Common gotchas (bugs → fixes)\n│ - Architectural decisions\n│\n└── progress.md # What's done, what's left\n - Completed items (with evidence)\n - Remaining tasks\n - Blockers\n```\n\nThe live namespace is `.cc10x/` (memory `.cc10x/*.md`, workflow state `.cc10x/workflows/*`). Two legacy residue locations are ignored by current router hydration if present: `.claude/cc10x/` (pre-10.1.20, before the workflow state moved out of `.claude/` to escape the harness sensitive-file gate) and the version-segmented `.cc10x/v10/` layout (v10.x, before the namespace was de-versioned in v11). cc10x does not migrate either; a fresh `.cc10x/` is created on first use.\n\n**Iron Law:** Every workflow loads memory at START and updates at END.\n\n---\n\n## Optional MCP Integrations\n\ncc10x works out of the box with no MCPs required. These are **optional** — they unlock specific features when installed in your own Claude Code MCP settings.\n\n| MCP | Feature Unlocked | How to Install |\n| ----- | ----------------- | ---------------- |\n| **[octocode](https://github.com/nicepkg/octocode)** | GitHub research: find packages, search code across repos, read PR history. Triggered automatically when planner or bug-investigator needs external research. | Install via Claude Code MCP settings using the server name `octocode` |\n| **[brightdata](https://github.com/nicepkg/mcp-brightdata)** | Web scraping for research tasks — used as fallback when web content is needed beyond GitHub. | Install via Claude Code MCP settings using the server name `brightdata` |\n\n**Important:** CC10X no longer ships MCP server config inside the plugin. This avoids startup warnings for users who do not have Bright Data or Octocode credentials configured.\n\n**Without these MCPs:** cc10x still works fully. The research agents degrade to built-in Claude Code tools and note the lower-confidence path in their outputs.\n\n**With octocode installed:** When the router detects new/unfamiliar tech, 3+ failed debug attempts, or explicit research requests, it automatically calls octocode tools to search GitHub before invoking the planner or bug-investigator.\n\n---\n\n## Troubleshooting\n\n### Claude Code keeps asking for permission to edit memory files\n\nAdd these two lines to `~/.claude/settings.json` under `permissions.allow`:\n\n```json\n\"Edit(.cc10x/*)\",\n\"Write(.cc10x/*)\"\n```\n\nThese permission examples cover the live `.cc10x/` namespace.\n\nOr run **\"Set up cc10x for me\"** again — the setup wizard adds them automatically.\n\n---\n\n### cc10x asks for permission before writing plan/research docs\n\nWorking as intended. `.cc10x/` orchestration state is pre-permitted, but outward-facing project artifacts (`docs/plans/`, `docs/research/`, `docs/solutions/`) prompt for approval by design — trust-first friction, not missing configuration. Approve the write to continue.\n\n---\n\n### cc10x not activating in a specific project\n\nThe global `~/.claude/CLAUDE.md` activates cc10x in every project — you only need one install. If it's not activating in a specific project:\n\n1. **Check if that project has its own `.claude/CLAUDE.md`** — open it and verify the cc10x section is present. If the project-level file exists but doesn't have the cc10x entry, add it there.\n2. **Verify the entry format** — use `[CC10x]|entry: cc10x:cc10x-router` (plugin reference). A relative path like `./plugins/cc10x/...` only works in the cc10x repo itself, not in your projects.\n3. **Restart Claude Code** — the plugin system requires a restart after any CLAUDE.md change.\n\n---\n\n### Ubuntu / Linux install error: EXDEV cross-device link\n\nIf you see:\n\n```\nError: Failed to install: EXDEV: cross-device link not permitted\n```\n\nThis is a Linux filesystem issue — `/tmp` and your home directory are on different filesystems, so the installer can't `rename()` across them. Fix:\n\n```bash\n# Set TMPDIR to a directory on the same filesystem as your home:\nmkdir -p ~/.claude/tmp\nTMPDIR=~/.claude/tmp claude\n# Then install normally: /plugin install cc10x@cc10x\n```\n\nIf that doesn't work, install manually:\n\n```bash\n# Clone directly into the plugins directory\ngit clone https://github.com/romiluz13/cc10x.git ~/.claude/plugins/cc10x\n```\n\nThen follow Step 2 in the setup guide above to add the cc10x entry to `~/.claude/CLAUDE.md`.\n\n---\n\n### \"Unknown skill cc10x:cc10x-router\"\n\nThe cc10x plugin is disabled. Run:\n\n```\n/plugins enable cc10x\n```\n\nThen retry your command.\n\n---\n\n## Architecture Deep Dive\n\nEverything below the fold: how the loop actually works. For contributors and the curious — you do not need any of this to use cc10x.\n\n\n cc10x v12.8.0
\n The Intelligent Orchestrator for Claude Code\n