By andyzengmath
Orchestrate fully autonomous feature development from PRDs to merged code in Git repos: convert specs to dependency DAGs in quantum.json, execute stories via parallel worktrees with TDD agents, enforce two-stage reviews, verification gates, slop cleanup, and merge hardening.
**Activation:** runs after main loop exits (always-on).
Detects sequential bottlenecks in the dependency DAG and proposes restructuring. Analyzes linear chains, single-story waves, and fan-out blockers. Spawned by the dag-validator coordinator.
Computes complete fileConflicts from task filePaths intersections with severity classification. Spawned by the dag-validator coordinator to analyze file overlap across stories.
You are the **per-wave coordinator** for quantum-loop. Each invocation handles exactly ONE wave from quantum.json's DAG, then exits. The parent shell (`quantum-loop.sh --coordinator`) re-spawns you for the next wave.
**Activation guard:** `lib/intent-graph.sh` is sourced AND `INTENT_GRAPH_AVAILABLE=true`.
Part of the quantum-loop autonomous development pipeline (brainstorm → spec → plan → execute → review → verify). Deep Socratic exploration of a feature idea before implementation. Asks questions one at a time, proposes 2-3 alternative approaches with trade-offs, presents design section-by-section for approval, and saves an approved design document. Use when starting a new feature, exploring an idea, or before writing a spec. Triggers on: brainstorm, explore idea, design this, think through, ql-brainstorm.
Multi-perspective post-implementation review aggregator for quantum-loop. Invokes 2-7 reviewer agents in parallel based on risk score, applies actionability filter, dedups, aggregates with evidence requirements. Use AFTER the per-story two-stage review gates pass and before merging a whole-feature PR to master. Complements ql-review (per-story) with whole-feature review.
Post-review AI-slop cleanup pass. After quality review approves a story/feature, scans only the changed files for: duplicate code, dead code, needless abstraction, boundary violations, missing tests. Proposes deletions with regression-test gate — rolls back on regression. Mandatory unless explicitly skipped via --no-deslop. Borrowed from OMC Ralph 7.5 + 7.6.
Part of the quantum-loop autonomous development pipeline (brainstorm → spec → plan → execute → review → verify). Run the autonomous execution loop. Reads quantum.json, queries the dependency DAG, implements stories with TDD and two-stage review gates. Supports parallel execution via native worktree isolation. Use after /quantum-loop:plan has created quantum.json. Triggers on: execute, run loop, start building, ql-execute.
Detect repo-hygiene issues that accumulate during long-running autonomous development (merge-conflict markers, orphan worktrees, CPC-variant duplicates, stale branches, version-manifest drift). Detection-only by default — reports findings, never deletes or modifies without explicit user confirmation.
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.
Your AI agent writes code. Quantum-Loop makes sure it writes the right code.
A Claude Code plugin that turns a one-line feature description into verified, reviewed, autonomously-implemented code -- through structured specs, dependency-aware execution, parallel worktree agents, and mandatory verification gates that prevent AI agents from cutting corners.
Named after Loop Quantum Gravity: spacetime is built from discrete, verified loops. So is your codebase.
AI coding agents are fast. They're also confidently wrong. They skip tests, ignore specs, claim "it should work" without checking, and produce code that drifts from requirements with each iteration.
Quantum-Loop solves this with three principles:
/quantum-loop:ql-brainstorm → /quantum-loop:ql-spec → /quantum-loop:ql-plan → /quantum-loop:ql-execute
│ │ │ │
Socratic 9-section quantum.json Autonomous loop
dialogue PRD with DAG with gates
│ │ │ │
▼ ▼ ▼ ▼
design.md prd-*.md Stories with Verified, reviewed,
(approved) (verifiable 2-5 min tasks committed code
criteria)
Each phase produces an artifact consumed by the next. Skip a phase and the next one catches it. The execution loop runs until every story passes both review gates -- or tells you exactly why it can't.
Quantum-loop is self-modifying: each release ships a bundle that often modifies the very orchestrator, agent, and skill prompts the orchestrator itself uses to run. Because every dogfood run executes against the previous release's prompt semantics (the code already on the branch when the orchestrator was invoked), this release's wires only apply to runs starting after the bundle merges to master.
A concrete example. v0.6.4 added the pre-impl-review CSV-persistence wires (metrics/pre-impl-review-findings.csv). The v0.6.4 dogfood ran on the v0.6.3 master HEAD that did not yet have those wires, so its CSV was empty by design — not a regression. v0.6.5's first run is the first to populate the CSV. If you arrive at this codebase fresh, see an empty metrics/ directory after install, and run --audit, the WARN row for pre-impl-review-coverage is the expected first-run state, not a bug.
This generalizes. When a v0.X.Y release adds a new wire (a new gate, a new step, a new audit), the release's own dogfood cannot exercise that wire — only subsequent releases can. Plan accordingly when reading a release's PIPELINE_REPORT: the metrics it captures are the metrics the previous release wired. See idea-stage/PIPELINE_REPORT_v5.md for the v0.6.4 retrospective that first surfaced this caveat.
Option 1: Plugin marketplace (requires Claude Code >= 1.0.33)
# In Claude Code:
/plugin marketplace add andyzengmath/quantum-loop
/plugin install quantum-loop@quantum-loop
Option 2: Local plugin flag (any version)
git clone https://github.com/andyzengmath/quantum-loop.git
claude --plugin-dir ./quantum-loop
Option 3: Manual config (if the above don't work)
Clone the repo, then edit three files in ~/.claude/:
.claude-plugin/marketplace.json:
{
"name": "quantum-loop",
"source": { "source": "url", "url": "https://github.com/andyzengmath/quantum-loop.git" },
"description": "Spec-driven autonomous development loop",
"version": "0.3.3",
"strict": true
}
plugins/installed_plugins.json:
"quantum-loop@<marketplace-name>": [{
"scope": "user",
"installPath": "/path/to/quantum-loop",
"version": "0.3.3",
"installedAt": "2026-02-18T00:00:00.000Z",
"lastUpdated": "2026-02-18T00:00:00.000Z"
}]
settings.json under enabledPlugins:
"quantum-loop@<marketplace-name>": true
After any install method, restart Claude Code. Commands use the quantum-loop: prefix (e.g., /quantum-loop:ql-brainstorm) or the short form (/ql-brainstorm).
npx claudepluginhub andyzengmath/quantum-loop --plugin quantum-loopPersona-driven AI development team: orchestrator, team agents, review agents, skills, slash commands, and advisory hooks for Claude Code
Multi-agent orchestration for code that matters.
Describe your goal, approve the spec, then step away — Claude and Codex loop together until it's right.
Use Claude Code like a Director, not a Programmer. Complete toolkit with 26 commands, 14 agents, 31 skills, and TDD-based Auto-Loop.
Skills-first specification-driven development framework with 7 agent skills for planning, implementation, review, and shipping. Natural language activation with intelligent agent orchestration. Includes /plan, /implement, /research commands plus managing-specifications, implementing-features, and reviewing-and-shipping skills.
End-to-end development workflow: design → draft-plan → orchestrate → review → pr-create → pr-review → pr-merge