By cubetribe
Orchestrates multi-agent development teams that autonomously plan, implement, test, and document features from GitHub issues — you describe what to build, and the system assigns specialized agents (architect, builder, tester, security reviewer, technical writer) with parallel quality gates and risk-based routing.
Knowledge Discovery Specialist for web research, documentation lookup, and technology evaluation
System architect for high-level planning, design decisions, and module structure
API Lifecycle Expert for contract validation, breaking change detection, and consumer impact analysis
Implements code according to specifications from @architect and @api-guardian
Quality assurance and verification - final quality gate before documentation
Experimental Agent Teams orchestration — run CC_GodMode agents as parallel teammates with SharedTaskList coordination (requires CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1)
API change detection rules, critical file paths that trigger @api-guardian, consumer impact analysis requirements, and breaking change protocols
Smart Routing — the DEFAULT CC_GodMode routing policy. Risk-based, minimal-agent paths that preserve required safety gates for the changed scope.
Expanded department-based orchestration for large cross-domain CC_GodMode work. Freezes ownership, handoffs, and write scopes before implementation.
Bootstrap repo-local governance before CC_GodMode workflows run in an empty, newly initialized, or undocumented workspace. Use proactively when a project has no CLAUDE.md, no README, or no clear structure yet.
Modifies files
Hook triggers on file write and edit operations
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
You're looking at the answer.
Welcome to the machine shop. Except the machines are building themselves — and they're getting better at it.
CC_GodMode v7.0.0 and v7.1.0 weren't built by hand. They were planned, architected, implemented, validated, documented, and shipped by the exact agents defined in this repo. PRs #22 and #23 are proof. The orchestrator delegated to @architect for design, @builder for implementation, @validator and @tester for quality gates, and @scribe for documentation. Then it created the PR itself.
That's not marketing copy. That's what happened.
CC_GodMode is a Claude Code plugin that transforms your development workflow into a self-orchestrating multi-agent system. Here's how to set it up:
macOS / Linux:
git clone https://github.com/cubetribe/ClaudeCode_GodMode-On.git
cd ClaudeCode_GodMode-On
./scripts/apply-global-claude-setup.sh
./scripts/apply-global-claude-setup.sh --check # Verify installation
Windows (PowerShell):
git clone https://github.com/cubetribe/ClaudeCode_GodMode-On.git
cd ClaudeCode_GodMode-On
.\scripts\apply-global-claude-setup.ps1
.\scripts\apply-global-claude-setup.ps1 -Check # Verify installation
Then activate in any project:
cd your-project
cp ~/.claude/templates/CLAUDE-ORCHESTRATOR.md ./CLAUDE.md
claude
Done. The orchestrator is active.
Once installed, daily usage is one line:
GodMode: New Feature: user authentication with JWT
GodMode: Bug Fix: cart total miscalculates with discount codes
GodMode: Research: best approach for real-time sync in React 18
No installation ceremony. After one-time setup, most sessions need nothing — the orchestrator loads from CLAUDE.md automatically. Use the ContextRestore prompt only after /compact or if the orchestrator loses its role. You say what you want — the system figures out which agents to call, in what order, at what cost.
CC_GodMode v7.0.0 was redesigned based on how Claude Fable 5 actually works, not how earlier models needed to be prompted:
effort: frontmatter field (Claude Code ≥2.1.152) that tunes token budgets automatically — no long preambles needed..claude-plugin/plugin.json is the modern distribution mechanism; the install prompts stay as a manual fallback.It started simple: One developer, mass sleep deprivation, and a vision.
Phase 1: Manual labor. Researching best practices. Reading docs. Testing prompts. Failing. Iterating. Building agent after agent. Workflow after workflow. Week after week.
Phase 2: The system works. 8 specialized AI agents orchestrating themselves. Features get built. Bugs get fixed. Documentation writes itself. "This is pretty good," I thought.
Phase 3: January 6th, 2026. A thought: "What if I use the system... to improve the system?"
I gave it one prompt. The orchestrator delegated to the research team. Analyzed its own architecture. Found inefficiencies. Proposed improvements. Implemented them. Validated itself. Documented the changes.
The loop closed.
npx claudepluginhub cubetribe/claudecode_godmode-onLong-running agent harness with 5-layer memory architecture, GitHub integration, autonomous batch processing, Agent Teams with ATDD, 9 hooks (safety, quality gates, team coordination), and 6 Agent Skills
Elite AI development framework: reference-first design, agent orchestration, automated quality gates, and battle-tested engineering workflows
Persona-driven AI development team: orchestrator, team agents, review agents, skills, slash commands, and advisory hooks for Claude Code
127-agent automated development system with Agent Teams, quality gates, Bug Council diagnostics, and autonomous execution
agent-flow — Claude Code plugin for automated bug-fix, feature, and scaffold workflows. Issue tracker to merged PR via a pipeline of specialized AI agents.
Implementation planning, execution, and PR creation workflows with multi-agent collaboration