claude-godmode

  ___  _                 _         ___            _       __  __             _
 / __|| | __ _  _  _  __| | ___   / __| ___   __| | ___ |  \/  | ___   __| | ___
| (__ | |/ _` || || |/ _` |/ -_) | (_ |/ _ \ / _` ||___|| |\/| |/ _ \ / _` |/ -_)
 \___||_|\__,_| \_,_|\__,_|\___|  \___|\___/ \__,_|     |_|  |_|\___/ \__,_|\___|

Production-grade engineering workflow for Claude Code. Ship features, not prompts.

Claude God-Mode

Claude God-Mode is a Claude Code plugin that ships rules (focused config files injected at session start), agents (specialized Claude instances with dedicated prompts, models, and memory), skills (slash-command workflows), and hooks (shell scripts on session events). Rules are individual concern-scoped files injected automatically by the SessionStart hook rather than a monolithic config, so you can read or extend any aspect independently. Your personal CLAUDE.md is never modified.

• Single clear workflow -- go from idea to merged PR with /mission → /brief N → /plan N → /build N → /verify N → /ship
• Quality gates enforcement -- typecheck, lint, test, and security checks run automatically before anything ships
• Isolated worktrees -- agents write code in separate git worktrees so your main branch stays clean
• Language-agnostic -- auto-detects your toolchain (package manager, test runner, linter, formatter, build system)
• Rules-based config -- concern-scoped rules injected by the SessionStart hook in every mode, your CLAUDE.md is never touched
• Persistent memory -- agents remember project patterns, conventions, and gotchas across sessions

Table of Contents

• Who It's For
• Why Claude God-Mode?
• Getting Started
• Workflow
• Missions
• Agents
• Skills
• Standalone Workflows
• Hooks
• Bundled MCP Servers
• Bundled LSP Servers
• Rules-Based Configuration
• Agent Memory
• Customization
• Troubleshooting
• FAQ
• Contributing
• License

Who It's For

Claude God-Mode is a Claude Code plugin for engineers who want a repeatable Claude Code workflow instead of ad-hoc prompting. Whether you're a solo developer or part of an engineering team, it brings code quality automation and AI engineering best practices to every session.

Solo developer shipping a feature. You have an idea, but turning it into a merged PR means juggling prompts, remembering to run tests, and hoping nothing slipped through. With God-Mode, you run /mission to set the goal, /brief N to define what to build, /plan N to break it into dependency-ordered steps, /build N to implement with automated review, /verify N to confirm every goal is covered, and /ship to push a clean PR -- all with quality gates enforced at every step.

Team standardizing their AI workflow. Your team uses Claude Code, but everyone prompts differently and quality varies. God-Mode's rules-based config gives every team member the same coding standards, testing protocols, and review process. The SessionStart hook injects the same baseline rules into every session, so the whole team gets identical behavior with no per-member setup.

Contributor extending the plugin. You want to add a new agent, skill, or rule. Each component is a self-contained markdown file with a clear contract. Drop a new agent into agents/, a new skill into skills/, or a new rule into rules/ -- the plugin picks it up automatically.

Why Claude God-Mode?

Claude Code is powerful out of the box. God-Mode adds structure -- the difference between a capable tool and a reliable workflow.

Without it, you write one-off prompts, manually enforce quality, and lose context between sessions. With it, you get a single clear workflow (/godmode through /ship), 18 specialized agents that handle implementation, review, testing, security, and architecture, and persistent memory that carries project knowledge across sessions. Quality gates (typecheck, lint, test, secrets scan) run on every change automatically -- not when you remember to ask.