Multi-agent autonomous development loop for Claude Code
Discovery • Planning • Implementation • Review • Repeat
Nazgul runs a complete autonomous SDLC pipeline — from scanning your codebase to shipping reviewed code — with 17 core agents plus project-specific reviewers.
- Auto-detects your project — classifies it (greenfield, brownfield, bugfix, refactor, migration) and tailors the pipeline
- Generates docs before code — PRDs, TRDs, and ADRs so agents build with context
- Multi-agent review board — Architect, Security, Code Quality + project-specific reviewers must ALL approve every task
- Fix-first review — auto-fixes mechanical issues (dead code, style), only asks about risky changes (security, architecture)
- Per-stage model routing — assign Opus, Sonnet, or Haiku to each pipeline stage for the right balance of cost, speed, and quality
- Survives interruptions — checkpoints, recovery pointers, session tracking, and hooks mean you can close your laptop and resume later
From the Orodruin Labs marketplace (recommended):
/plugin marketplace add OrodruinLabs/nazgul
/plugin install nazgulDirect install from GitHub:
/plugin install nazgul@github:OrodruinLabs/nazgulManual install (for development or pinning a specific version):
git clone https://github.com/OrodruinLabs/nazgul.git ~/.claude/plugins/nazgulUpdate:
/plugin # Select nazgul → "Update now"Or enable auto-updates: /plugin → Marketplaces tab → orodruin-labs → Enable auto-update.
Tip
3 commands to get started:
/nazgul:init # Set up Nazgul for your project
/nazgul:start # Start the autonomous loop
/nazgul:status # Check progress anytimeNazgul auto-detects project state: active work resumes, existing docs trigger planning, fresh projects scan for TODOs/issues/failing tests. Override with /nazgul:start "specific objective".
Warning
Autonomous mode skips all permission prompts:
claude --dangerously-skip-permissions
/nazgul:start --yolo --max 30| Command | Description |
|---|---|
/nazgul:init |
First-time setup: discovery, reviewer generation, runtime dirs |
/nazgul:start |
Smart start/resume — auto-detects state, derives objective |
/nazgul:status |
Check loop progress, task counts, reviewer board |
/nazgul:pause |
Gracefully pause at next iteration boundary |
/nazgul:task |
Task lifecycle: skip, unblock, add, prioritize, list |
/nazgul:review |
Manually trigger review for a task |
/nazgul:log |
View run history — iterations, commits, reviews |
/nazgul:board |
Connect task tracking to GitHub Projects |
/nazgul:docs |
View or regenerate project documents |
/nazgul:config |
View and change settings (models, formatter, notifications) |
/nazgul:enhance |
Research Claude Code releases, propose Nazgul improvements |
/nazgul:metrics |
View loop performance — velocity, approval rates, self-improvement reports |
/nazgul:verify |
Human acceptance testing for completed tasks |
/nazgul:help |
Quick reference for all commands and modes |
/nazgul:bootstrap-project |
Generate a portable, Nazgul-free bundle (docs + Claude subagents) |
See /nazgul:help for the full command list and all flags.
Different pipeline stages have different complexity needs. Nazgul lets you assign the right model to each stage:
| Stage | Default | Why |
|---|---|---|
| Planning | Opus | Decomposition and dependency ordering need deep reasoning |
| Discovery | Sonnet | Codebase scanning is pattern matching |
| Docs | Sonnet | Technical writing is well within Sonnet's capability |
| Review | Sonnet | Structured checklists, Sonnet handles them well |
| Implementation | Sonnet | Code generation is Sonnet's sweet spot |
| Specialists | Sonnet | Same as implementation |
| Post-loop | Haiku | Changelog and docs updates are mechanical |
Configure during init or anytime after with /nazgul:config:
/nazgul:config models # Jump straight to model settingsThree presets available: Balanced (default), Quality (all Opus), and Fast/cheap (Haiku where possible). Or pick per stage.
/nazgul:bootstrap-project runs the pre-planning pipeline once and outputs a portable bundle — no Nazgul dependency required. You get project docs, codebase context, and tailored Claude subagents that work with plain Claude Code.
What it generates:
./docs/— PRD, TRD, ADRs./docs/context/— Codebase analysis from Discovery./.claude/agents/— Project-specific reviewer agents
Usage:
/nazgul:bootstrap-project "your objective"All Nazgul references are scrubbed from the output. Won't run if ./nazgul/ exists (use /nazgul:start for full pipeline instead).
Nazgul runs a pipeline of specialized agents. Discovery scans your codebase and classifies the project. The Doc Generator creates foundational documents. The Planner decomposes your objective into dependency-ordered tasks. The Implementer builds each task (delegating to specialists like Frontend Dev, DevOps, or DB Migration as needed). A Review Board of 3-13 reviewers must unanimously approve each task before it advances — mechanical issues are auto-fixed, only risky changes require discussion. The loop continues until every task is done, then Post-Loop agents handle documentation, releases, and observability.
Agents can optionally self-rate their experience and file improvement reports, creating a feedback loop for plugin quality. Concurrent sessions are detected via filesystem locks to prevent state corruption.
See Architecture for the full agent roster, pipeline details, and recovery system.
jq— Required for JSON manipulation in hook scriptsgit— Required for commit tracking and state persistence- Claude Code — Agent Teams is enabled automatically by
/nazgul:init
- Architecture — Pipeline, agent roster, recovery, directory structure
- Configuration — Start flags, local mode, board sync
- Safety & Rules — The 10 rules, guardrails, troubleshooting
- Plugins — Companion plugins, compatibility matrix, OpenClaw
MIT