Legion plugin
Legion runs a project in plan, build and review phases with a team of 49 agent roles in Claude Code, Codex and Cursor.
- 82 ★ on the repository
- Last commit
Extended access
Why this level
- Parallel agent groups edit project files and create service files in `.planning/`.
- The installer writes files into agent directories, and into the home folder for a global install.
Install
- Works in
Manual install
npx @9thlevelsoftware/legion --claudeThe first README command. For another agent replace `--claude` with its runtime flag, for example `--codex` or `--cursor`.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Parallel agent groups edit project files and create service files in `.planning/`.
- The installer writes files into agent directories, and into the home folder for a global install.
This is third-party code. Review the repository files before installing.
What it does
Legion is a plugin that organizes the work of 49 agent roles on top of a CLI agent. A project goes through phases: `/legion:start` asks questions and creates `PROJECT.md` and `ROADMAP.md`, `/legion:plan` splits a phase into waves of tasks and picks a team, `/legion:build` executes the phase with parallel agent groups, `/legion:review` runs a review cycle with testers. Beyond the main loop there are quick tasks `/legion:quick`, expert advice `/legion:advise`, a codebase map `/legion:map`, a board of directors `/legion:board` for architecture decisions, release preparation `/legion:ship` and project memory `/legion:learn`. The `npx @9thlevelsoftware/legion` installer with a runtime flag lays files out for the chosen agent.
Who it is for. Teams and solo developers who run a big project with agents and want phases, roles and reviews instead of one long session.
Good fit when
- A new project starts with questions and a roadmap rather than code.
- A phase is split into waves of tasks executed by parallel agent groups.
- After a phase is built, a review cycle with testing agents runs.
- An architecture decision goes to a board of specialized roles.
Not a fit when
- One small edit is needed: the overhead of phases and plans will not pay off.
- Cursor, Windsurf or Aider is used: support there is experimental.
- A clear license is required: GitHub detected none for the repository.
Example request
Run /legion:start for this repository and draft the project roadmap.Limitations
Node.js 18 or newer is required. Support levels vary: Claude Code and Antigravity are certified, Codex, Copilot CLI, Gemini CLI, Kiro, OpenCode and Kilo are beta, Cursor and Windsurf are experimental with project-level rules only, Aider is manual only. Native `/legion:*` commands do not work everywhere, and the compatibility table is in `docs/runtime-audit.md`. GitHub detected no license. The README heading points to a newer project, Legion Ascended. The last commit was made on 16 September 2026.
How to disable. Delete the Legion files from the agent directory, for example the project `.claude/`, and the `.planning/` folder with project state. For a global install delete them in the agent home folder.
FAQ
How do I install Legion for Claude Code?
With `npx @9thlevelsoftware/legion --claude`. For Codex add `--codex`, for Cursor `--cursor`, for Gemini CLI `--gemini`.
How do I run Legion in Codex?
A local install gives `/project:legion-start`, `/project:legion-plan` and `/project:legion-build`, a global one `/prompts:legion-start`. The old `/legion:*` stay as fallback aliases.
Which phases does a project go through?
Start, plan, build and review. After `/legion:start` the project gets `PROJECT.md` and `ROADMAP.md`, then `plan`, `build` and `review` repeat for each phase.
Can I use it without phases?
Yes. `/legion:quick` runs a one-off task with agent selection, and `/legion:advise` gives expert consultation without touching files.
Where is the project state stored?
In the `.planning/` folder. The `/legion:validate` command checks the integrity of these files, and `--fix` repairs what it finds.
Discussion
No questions or reviews yet.
Related
PluginsA one-person coding factory: Claude Code manages the project while Codex, Qwen, Grok and Kimi write code as separate processes.
Squad creates coding-agent teams with roles and shared repository memory for distributing tasks and retaining decisions.
Multi-agent orchestration for Claude Code: teams, roles, autopilot and task routing across skills and subagents
A desktop app where Claude Code, Codex, Gemini and other agents work as a team of specialists in a shared project
A template sets up a multi-agent environment in a repository: Claude Code conducts Sonnet and Opus subagents and calls Codex CLI.
Argus runs long engineering and research tasks with four roles, where a reviewer reads results but edits nothing.
README in short
The README explains installation for fourteen runtime options, support tiers, entry points in each agent, the path from start to release and a list of nineteen commands. Codex installation and the repository Codex plugin are described separately.