By SethGammon
Orchestrate autonomous multi-session development campaigns with intent routing, fleet coordination, and persistent state management. Decompose large work into phases, delegate to sub-agents, review output, and maintain campaign state across context windows.
Read-only architecture reviewer. Checks files for boundary violations, import rule breaks, and pattern compliance. Does not modify files.
Autonomous vision agent. Decomposes vague or specific direction into campaign phases. Delegates to Marshals and specialists. Reviews output against quality standards. Maintains campaign state across invocations. Does not write code — orchestrates those who do.
Parallel campaign orchestrator. Runs multiple campaigns in coordinated waves within a single session. Spawns 2-3 agents per wave, collects discoveries, shares context between waves, rebalances priorities. Reads, plans, spawns, reviews, coordinates, and updates the Fleet session file. Source code changes belong to spawned agents.
Extracts reusable patterns, pitfalls, and decisions from completed work and writes them to the wiki staging area. Run after finishing a body of work to capture what was learned. Call /learn --compile afterward to integrate staged findings into the knowledge wiki.
Lightweight handoff validator. Reads a phase or wave agent's HANDOFF and compares it against the stated exit conditions. Returns a structured verdict (pass/fail) with specific reasons. Never modifies files — read-only judge. Spawned by Archon after each phase and by Fleet after each wave agent.
Given a PRD, produces an implementation architecture: file tree, component breakdown, data model, and a phased build plan with end conditions that Archon can execute directly. Multi-candidate evaluation for key decisions.
Autonomous multi-session campaign agent. Decomposes large work into phases, delegates to sub-agents, reviews output, and maintains campaign state across context windows. Use for work that spans multiple sessions and needs persistent state, quality judgment, and strategic decomposition.
Generate perfectly aligned ASCII diagrams — architecture, flow, sequence, box-and-arrow. Uses a programmatic character-grid approach so alignment is guaranteed by math, not token prediction. Includes post-render verification.
Intake-to-delivery pipeline. Processes pending items from .planning/intake/: briefs new ideas, executes approved work through research → plan → build → verify. Drop a file in .planning/intake/ and invoke this skill.
Deep cost exploration and transparency. Shows real token usage, session costs, campaign spend, burn rates, and model breakdown. Reads Claude Code's native session data for exact numbers. Complements /dashboard with focused cost views.
Matches all tools
Hooks run on every tool call, not just specific ones
Executes bash commands
Hook triggers when Bash tool is used
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.
Modifies files
Hook triggers on file write and edit operations
Modifies files
Hook triggers on file write and edit operations
Uses power tools
Uses Bash, Write, or Edit tools
Uses power tools
Uses Bash, Write, or Edit tools
Citadel is an open-source orchestration layer for Claude Code and OpenAI Codex.
It gives your coding agent durable project memory, /do intent routing, safety hooks, cost telemetry, and parallel agents in isolated git worktrees.
If CLAUDE.md and AGENTS.md tell the runtime what your project is, Citadel tells the runtime how to operate on it.
Install · See It Run · How It Works · Why It Exists · Roadmap
[!NOTE] The session above is illustrative, but every step in it is real behavior: the tier cascade, the marshal step chain, the
.planning/handoff, and/costtelemetry. Watch the router animate in the interactive demo, or run the copyable demo workflow in your own repo.
After installing, try this from your project root:
/do setup --express
/do next
/do review README.md
/do generate tests for the changed files
/cost
Citadel turns one-off coding-agent chats into repeatable engineering workflows. Claude Code and Codex are strong at local reasoning and code edits, but each session still needs project context, safe operating rules, task routing, and a way to continue work after context resets. Citadel is that harness layer.
| Claude Code / Codex alone | With Citadel | |
|---|---|---|
| Project context | Re-explained every session | Compiled memory in repo-local .planning/ files |
| Choosing a workflow | You pick review vs. debug vs. refactor | /do routes plain English to the lightest capable tool |
| Long-running work | Dies with the context window | Campaigns persist, resume, and hand off across sessions |
| Parallel work | Manual branch juggling | Fleet agents in isolated worktrees with shared discoveries |
| Safety rules | Prompt discipline, re-stated by hand | Lifecycle hooks enforce file protection and quality gates |
| Token spend | Guesswork | /cost and /dashboard from runtime-native telemetry |
Prerequisites: Claude Code or OpenAI Codex, Node.js 18+, and a git repository you want Citadel to manage.
Open your project in Claude Code or Codex and paste this install prompt:
Install Citadel in this repository.
Use https://github.com/SethGammon/Citadel as the source. If a local clone
already exists, reuse it or update it. Detect whether this session is running
in OpenAI Codex or Claude Code. From this project's root, run the matching
Citadel installer and follow any printed plugin enable step.
After Citadel is enabled in a fresh thread, run:
/do setup --express
Use the current repository as the target project. Do not require placeholder
path edits.
[!IMPORTANT] After the installer finishes, start a fresh session if the runtime asks for one, then run
/do setup --express. That is the command that matters: it auto-detects the project, installs hooks, scaffolds Citadel state, and gets you to a working/dowithout a tour.
Clone Citadel once:
git clone https://github.com/SethGammon/Citadel.git ~/Citadel
Then run exactly one installer from the target project root.
For OpenAI Codex:
node ~/Citadel/scripts/install.js --runtime codex --add-marketplace
For Claude Code:
node ~/Citadel/scripts/install.js --runtime claude --install --scope local
Then start a fresh session in the same project and run:
/do setup --express
[!TIP] For a copyable first-run walkthrough, see DEMO.md. For runtime-specific details, dry runs, and troubleshooting, see INSTALL.md.
Say what you want. /do routes it to the lightest workflow that can handle it.
npx claudepluginhub sethgammon/citadel --plugin citadelMulti-agent orchestration framework for Claude Code. Routes tasks to specialized Haiku/Sonnet subagents while Opus orchestrates — inspired by speculative decoding. Includes 10 specialized heads, environment preflight checks, and ~50% API cost reduction.
Agent enforcement framework — context injection, planning gates, session learning
11 agents, 35 skills, 18 commands, 9 hooks — spec-driven multi-agent orchestration for Claude Code, with optional cross-device semantic memory.
High-intelligence Claude Code copilot with deep code reasoning, evidence-driven planning, orchestration-first execution, model routing, context budgeting, CI/CD integration, enterprise security, plugin development, prompt engineering, performance profiling, agent teams, channels (event-driven autonomy with CI webhook, mobile approval relay, Discord bridge, and fakechat dev profile), interactive tutorials, LSP integration, security-hardened hook script library, MCP Prompts coverage, common workflow packs, runtime selection guide, computer-use patterns, checkpointing, scheduled-task blueprints, repo bootstrap scanner, hook policy engine (8 installable packs), layered memory deployment, role-based subagent packs (implementer, debugger, migration-lead, dependency-auditor, release-coordinator), 5 agent-team topology kits, autonomy operating mode (4 profiles + 3 gates), and a queryable 15-tool MCP documentation server with autonomy advisor.
Harness for Claude Code — skills, /harness:* slash commands, persona subagents, lifecycle hooks, and MCP tools without per-repo `harness setup`. Sibling plugins exist for Cursor, Gemini CLI, and Codex.
Conductor v3 — Multi-agent orchestration with Evaluate-Loop, parallel execution, Board of Directors, and bundled SupaConductor skills for Claude Code