{
  "id": "page:library-cc10x",
  "_kind": "Page",
  "_file": "wiki/library/cc10x.md",
  "_cluster": "wiki",
  "attributes": {
    "nodeKind": "Page",
    "title": "CC10X Methodology (Library)",
    "displayName": "CC10X Methodology (Library)",
    "slug": "library/cc10x",
    "articlePath": "wiki/library/cc10x.md",
    "article": "\n# CC10X Methodology\n\nIntelligent workflow orchestration for Claude Code development. CC10X routes all development requests through a single entry point that detects intent and dispatches to specialized workflows with evidence-first validation, TDD enforcement, and persistent session memory.\n\n## Core Principles\n\n1. **Single Entry Point**: The cc10x-router handles all requests -- no manual skill selection\n2. **Evidence-First**: All claims backed by logs, test results, or exit codes (zero = success)\n3. **TDD Enforcement**: RED-GREEN-REFACTOR is mandatory during builds; tests are never skipped\n4. **Memory Persistence**: Context survives across sessions via three memory surfaces\n5. **Confidence Gating**: Issues reported must reach >=80% confidence; vague feedback rejected\n6. **Parallel Execution**: Agents run simultaneously when possible (~30-50% faster)\n\n## Workflows\n\n| Workflow | Trigger | Agent Chain |\n|----------|---------|-------------|\n| **BUILD** | build, implement, create, make, write, add | component-builder -> [code-reviewer \\|\\| silent-failure-hunter] -> integration-verifier |\n| **DEBUG** | debug, fix, error, bug, broken, troubleshoot | bug-investigator -> code-reviewer -> integration-verifier |\n| **REVIEW** | review, audit, check, analyze, assess | code-reviewer (multi-dimensional) |\n| **PLAN** | plan, design, architect, roadmap, strategy | planner (with github-researcher) |\n\n## Process Files\n\n| File | Process ID | Description |\n|------|-----------|-------------|\n| `cc10x-router.js` | `methodologies/cc10x/cc10x-router` | Single entry point: intent detection, workflow dispatch, contract validation, memory persistence |\n| `cc10x-build.js` | `methodologies/cc10x/cc10x-build` | BUILD workflow: TDD cycle, parallel review, integration verification |\n| `cc10x-debug.js` | `methodologies/cc10x/cc10x-debug` | DEBUG workflow: log-first investigation, targeted fix, verification |\n| `cc10x-review.js` | `methodologies/cc10x/cc10x-review` | REVIEW workflow: 4-dimension parallel analysis with confidence scoring |\n| `cc10x-plan.js` | `methodologies/cc10x/cc10x-plan` | PLAN workflow: research, brainstorming, plan creation with build continuity |\n\n## Agents (8)\n\n| Agent | Role | Used In |\n|-------|------|---------|\n| `cc10x-router` | Intent detection and workflow orchestration | All workflows |\n| `component-builder` | TDD feature development | BUILD |\n| `bug-investigator` | Log-first root cause analysis | DEBUG |\n| `code-reviewer` | Multi-dimensional quality assessment | BUILD, DEBUG, REVIEW |\n| `silent-failure-hunter` | Error handling gap detection | BUILD |\n| `integration-verifier` | Evidence-backed E2E validation | BUILD, DEBUG |\n| `planner` | Comprehensive planning with research | PLAN |\n| `github-researcher` | GitHub repository and package research | PLAN, DEBUG |\n\n## Skills (8)\n\n| Skill | Purpose |\n|-------|---------|\n| `session-memory` | Context persistence across message compaction |\n| `verification-before-completion` | Evidence requirement enforcement |\n| `test-driven-development` | RED-GREEN-REFACTOR enforcement |\n| `code-generation` | Minimal, pattern-matching code output |\n| `debugging-patterns` | Root cause analysis frameworks |\n| `code-review-patterns` | Security, quality, performance assessment |\n| `planning-patterns` | Structured planning methodology |\n| `architecture-patterns` | System and API design guidance |\n\n## Memory System\n\nThree files in `.claude/cc10x/`:\n\n- **activeContext.md** -- current focus, decisions, learnings, blockers\n- **patterns.md** -- project conventions, gotchas, architectural decisions\n- **progress.md** -- completed work, remaining tasks, verification results\n\n## Router Contract\n\nEvery agent output includes a machine-readable contract:\n- **STATUS**: PASS, FAIL, APPROVE, REJECT, NEEDS_REMEDIATION\n- **BLOCKING**: whether workflow can proceed\n- **REQUIRES_REMEDIATION**: whether REM-FIX task is needed\n- **Issue counts**: critical and high severity tallies\n- **Memory notes**: items to persist for future sessions\n\n## Plan-to-Build Continuity\n\nPlans created by the PLAN workflow are saved to `docs/plans/` and referenced in session memory. The BUILD workflow reads these plans during the requirements clarification phase, ensuring consistency between strategy and execution.\n\n## Attribution\n\nAdapted from [CC10X](https://github.com/romiluz13/cc10x) by Rom Iluz.\n",
    "documents": [
      "specialization:cc10x"
    ]
  },
  "outgoingEdges": [
    {
      "from": "page:library-cc10x",
      "to": "specialization:cc10x",
      "kind": "documents"
    }
  ],
  "incomingEdges": [
    {
      "from": "page:index",
      "to": "page:library-cc10x",
      "kind": "contains_page"
    }
  ]
}