Give the shiny new thing a try at: https://9thlevelsoftware.github.io/legion-ascended

Legion

Orchestrate 49 AI specialist personalities across 10 AI CLI runtimes plus the Kilo Code plugin.

"My name is Legion, for we are many."

What It Does

Turn 49 isolated agent personalities into a coordinated legion. The native Legion entry point now depends on the runtime you install into. See the audited compatibility matrix in docs/runtime-audit.md before assuming /legion:* works everywhere.

Installation

Quick install (recommended)

npx @9thlevelsoftware/legion --claude

Replace --claude with your runtime of choice:

| Flag | Runtime | |------|---------| | --claude | Claude Code | | --codex | OpenAI Codex CLI | | --cursor | Cursor | | --copilot | GitHub Copilot CLI | | --gemini | Google Gemini CLI | | --antigravity | Antigravity CLI | | --kiro | Kiro CLI (preferred) | | --amazon-q | Deprecated alias for --kiro | | --windsurf | Windsurf | | --opencode | OpenCode | | --kilo | Kilo CLI | | --kilo-code | Kilo Code Plugin | | --kilocode | Alias for --kilo-code | | --aider | Aider (manual-only; native install disabled) |

Runtime Support Tiers

| Runtime | Status | Notes | |---------|--------|-------| | Claude Code | Certified | Control runtime with native Legion slash commands, agents, and skills | | OpenAI Codex CLI | Beta | Native prompt commands plus a Legion bridge skill; use /project:legion-start or /prompts:legion-start | | GitHub Copilot CLI | Beta | Native /legion-start skills plus a legion-orchestrator agent profile | | Google Gemini CLI | Beta | Native /legion:start custom commands in .gemini/commands/legion/ | | Antigravity CLI | Certified | Native /legion:start plugins in .agents/plugins/legion/ (local) or ~/.gemini/config/plugins/legion/ (global) | | Kiro CLI (formerly Amazon Q Developer CLI) | Beta | Native @legion-orchestrator custom agent plus steering files | | OpenCode | Beta | Native /legion-start custom commands plus a Legion subagent | | Kilo CLI | Beta | Native /legion-start custom commands plus a Legion subagent | | Kilo Code Plugin | Beta | Native Legion custom mode plus Legion workflows and Agent Skills in both .kilocode/ and CLI-backed .kilo/ paths; use --kilo-code instead of --kilo | | Cursor | Experimental | Local-only rules install in .cursor/rules/; plain-language Legion requests only | | Windsurf | Experimental | Local-only rules install in .windsurf/rules/; plain-language Legion requests only | | Aider | Experimental | Manual-only fallback; automated native install is intentionally disabled |

Local development

git clone https://github.com/9thLevelSoftware/legion.git
node bin/install.js --claude

Prerequisites

• Node.js 18+
• One of the 10 AI CLI runtimes listed above or Kilo Code plugin support via --kilo-code (support tier varies by runtime)

Codex note

If you install with --codex, Legion writes its workflow files into .legion/, installs native prompt commands into .codex/prompts/ for local installs or ~/.codex/prompts/ for global installs, and also installs a legion bridge skill into .agents/skills/legion/.

• Local Codex installs appear as /project:legion-start, /project:legion-plan, /project:legion-build, and so on
• Global Codex installs appear as /prompts:legion-start, /prompts:legion-plan, /prompts:legion-build, and so on
• Legacy /legion:* aliases remain bridge-only fallbacks, and plain-language Legion intents still work

Repo-native Codex plugin

This repository now also ships a repo-native Codex plugin manifest at .codex-plugin/plugin.json.

• Use the repo-native plugin path when you want Codex to load Legion directly from this checkout as a local plugin bundle
• The repo-native plugin exposes a top-level legion bridge skill at skills/legion/SKILL.md, which routes plain-language Legion requests and legacy /legion:* intents to the matching workflow under commands/
• This path is additive: it does not replace or modify the existing npx @9thlevelsoftware/legion --codex installer flow
• The npx installer remains the path that writes native Codex prompt commands into .codex/prompts/ or ~/.codex/prompts/

Native entry points

| Runtime | Local install | Global install | |---------|---------------|----------------| | Claude Code | /legion:start | /legion:start | | OpenAI Codex CLI | /project:legion-start | /prompts:legion-start | | GitHub Copilot CLI | /legion-start or /agent legion-orchestrator | /legion-start or /agent legion-orchestrator | | Google Gemini CLI | /legion:start | /legion:start | | Antigravity CLI | /legion:start | /legion:start | | Kiro CLI | @legion-orchestrator | @legion-orchestrator | | OpenCode | /legion-start | /legion-start | | Kilo CLI | /legion-start | /legion-start | | Kilo Code Plugin | Select Legion mode or run /legion-start.md or /legion-start | Select Legion mode or run /legion-start.md or /legion-start | | Cursor | Plain-language request after local rules install | Not supported | | Windsurf | Plain-language request after local rules install | Not supported | | Aider | Manual-only | Manual-only |

Getting Started

1. Install Legion (see above)
2. Start Legion with the runtime-native entry point from the table above
3. Answer the guided questions — or run /legion:explore first to create a design document
4. Review the generated PROJECT.md and ROADMAP.md
5. Plan the first phase with the runtime-native Legion plan entry
6. Execute the phase with the runtime-native Legion build entry
7. Review the phase with the runtime-native Legion review entry
8. Repeat plan → build → review for each phase

Commands

These are the canonical Legion command names. Each runtime maps them to its own discovery surface. Codex uses flat prompt names such as /project:legion-start; Gemini keeps /legion:start; Copilot, OpenCode, and Kilo CLI use flat /legion-start; Kilo Code Plugin installs both plugin workflows such as /legion-start.md and CLI-backed workflows such as /legion-start, plus a single Legion mode bridge and individual Agent Skills; Kiro uses @legion-orchestrator; Cursor and Windsurf rely on their installed rules and plain-language intent routing. Nineteen commands total.

| Command | Description | Usage | |---------|-------------|-------| | /legion:start | Initialize project with guided questioning | Run once at project start | | /legion:plan <N> | Plan phase N with agent recommendations and wave-structured tasks | After start, or after completing a phase | | /legion:build | Execute current phase with parallel agent teams | After planning a phase | | /legion:review | Run QA review cycle with testing/QA agents | After building a phase | | /legion:status | Show progress dashboard and route to next action | Anytime — routes you to the right command | | /legion:quick <task> | Run ad-hoc task with intelligent agent selection | Anytime — for one-off tasks | | /legion:advise <topic> | Get read-only expert consultation from any agent | Anytime — standalone advisory, no phase context needed | | /legion:portfolio | Multi-project dashboard with dependency tracking | When managing multiple projects | | /legion:milestone | Milestone completion, archiving, and metrics | At project milestones | | /legion:agent | Create a new agent personality through guided workflow | When you need a specialist that doesn't exist | | /legion:map | Generate, refresh, check, or query the codebase map dataset | Before start or planning in existing codebases | | /legion:explore | Research-first design discovery with Polymath | Creates a design doc; can hand off to /legion:start <design-doc> when you choose | | /legion:board | Convene board of directors for governance decisions | For architecture decisions, go/no-go calls, conflict resolution | | /legion:retro | Run structured retrospective on completed phases or milestones | After phases or milestones — captures what worked, what didn't | | /legion:ship | Pre-ship checklist, PR creation, deployment verification, canary monitoring | After review — formal shipping stage before the next phase | | /legion:learn | Record, recall, and manage project-specific patterns and preferences | Anytime — operationalizes project memory | | /legion:update | Check for updates and install latest version from npm | After installation — keeps Legion current | | /legion:polish | Run 4-pass code cleanup on changed files or a target path | After review, or anytime via ad-hoc invocation | | /legion:validate | Validate .planning/ state file integrity, schema conformance, and cross-references | Anytime — catches drift and corruption early (supports --ci, --fix) |

How It Works

/legion:start            Guided questioning → PROJECT.md + ROADMAP.md
       ↓
/legion:plan 1           Phase decomposition → Wave-structured plans + agent teams
       ↓                       ↓ (optional)
       ↓                 Plan critique → Pre-mortem + assumption hunting
       ↓
/legion:build            Parallel execution → Agents work in character, wave by wave
       ↓
/legion:review           Quality gate → Review → Fix → Re-review (default max 3 cycles, configurable)
       ↓                       ↓ (optional)
       ↓                 Panel mode → 2-4 domain-weighted reviewers with rubrics
       ↓                       ↓ (post-review, configurable)
       ↓                 Code polish → 4-pass cleanup (comments, simplification, readability, consistency)
       ↓
/legion:ship             Ship pipeline → Pre-ship gates → PR creation → deployment verification
       ↓
/legion:retro            Retrospective → What worked, what didn't, reusable patterns
       ↓
/legion:plan 2 → ...     Repeat for each phase until project complete


/legion:map              Standalone →