LEGION

"My Name Is Legion, For We Are Many"

52 AI Specialist Personalities. 9 CLI Runtimes. One Coordinated Force.

Legion is a multi-CLI orchestrator that binds 52 specialist personalities into a single coordinated force. Engineers, designers, marketers, testers, product leads, project managers, and more — each with deep expertise, distinct voice, and hard-earned opinions. Speak the word, and the many answer as one.

52
Agents
9
Divisions
9
CLIs
11
Commands
17
Skills
0
Dependencies

Summon the Legion

Install with npx, open any project, and speak: /legion:start
The many will answer.

# Install for Claude Code
npx @9thlevelsoftware/legion --claude

# Or for other runtimes:
npx @9thlevelsoftware/legion --codex      # OpenAI Codex CLI
npx @9thlevelsoftware/legion --cursor     # Cursor
npx @9thlevelsoftware/legion --gemini     # Google Gemini CLI
# + copilot, amazon-q, windsurf, opencode, aider

# Then, in any project directory:
/legion:start            # And the many awaken

The Fifty-Two

Not generic role labels. Each is an 85–348 line character sheet with deep expertise, communication style, hard rules, and personality quirks. When summoned, each receives its complete personality as instructions.

8

Engineering

Full-stack, backend, frontend, AI, DevOps, mobile, prototyping, Laravel

6

Design

UI/UX, branding, visual storytelling, UX research, whimsy

8

Marketing

Content, social media, growth, TikTok, Reddit, Instagram, ASO

7

Testing

QA, evidence collection, performance, API testing, tool evaluation

3

Product

Sprint planning, feedback synthesis, trend research

5

Project Management

Coordination, portfolio, operations, experiments, production

6

Support

Analytics, finance, legal, infrastructure, executive summaries

6

Spatial Computing

VisionOS, XR, Metal, terminal integration, cockpit UI

3

Specialized

Orchestration, data analytics, LSP indexing

The Commands

Eleven commands. Each a word of power.

CommandPurpose
/legion:startInitialize a new project with guided questioning flow
/legion:plan <N>Plan phase N with agent recommendations and wave-structured tasks
/legion:buildExecute current phase with parallel agent teams
/legion:reviewRun quality review cycle with testing/QA agents
/legion:statusShow progress dashboard and route to next action
/legion:quick <task>Run ad-hoc task with intelligent agent selection
/legion:advise <topic>Get read-only expert consultation from any personality
/legion:portfolioMulti-project dashboard with dependency tracking
/legion:milestoneMilestone completion, archiving, and metrics
/legion:agentCreate a new agent personality through guided workflow
/legion:updateCheck for updates and install latest version from npm

The Rite of Execution

Each phase follows the sacred cycle: plan, build, review. Within each wave, agents work in parallel. Between waves, they synchronize.

/legion:start Guided questioning → PROJECT.md + ROADMAP.md
/legion:plan 1 Phase decomposition → Wave-structured plans + agents
/legion:build Parallel execution → Agents work in character, wave by wave
/legion:review Quality gate → Review → Fix → Re-review (max 3 cycles)
/legion:plan 2 Next phase → Repeat until the work is done

The Sacred Powers

Personality Injection

Each of the 52 agents is spawned with its complete 85–348 line character sheet as system instructions. Not a role label — an identity.

Wave Execution

Plans are grouped into dependency waves. Everything within a wave runs in parallel. Between waves, synchronization. Maximum throughput, zero conflicts.

Hybrid Selection

The system recommends agents based on keyword matching, division affinity, and past performance. You always confirm or override. No black-box assignments.

Domain Detection

Marketing phase? Campaign planning activates. Design phase? Three-lens review (brand + accessibility + usability). Engineering isn't the only workflow.

Quality Gates

Structured dev-QA loop: review → fix → re-review. Hard cap at 3 cycles. If it still fails, the problem is systemic — escalate to human.

Review Panels

2–4 domain-weighted reviewers with non-overlapping rubrics. Max 2 from any division. At least one tester on every panel. Diversity by design.

Plan Critique

Pre-mortem analysis assumes the phase has already failed, then works backward. Assumption hunting flags high-impact, weak-evidence beliefs.

Cross-Session Memory

Outcomes recorded after each cycle. During future planning, past performance boosts agent recommendations — with time-based decay so the system evolves.

Read-Only Advisory

/legion:advise spawns any personality as a read-only consultant. Full character, full expertise, zero risk. Tool-level enforcement via Explore agents.

Atomic Commits

Every completed plan produces an independent commit. If Plan 2 breaks something, roll it back without losing Plan 1. Clean revert boundaries.

Graceful Degradation

GitHub integration, memory, brownfield analysis, marketing workflows, design workflows, panels, critique — all opt-in. The core loop works without any of them.

Zero Runtime Dependencies

No custom CLI. No MCP server. No shell hooks. Zero runtime dependencies — npm is install-time only. Skills, commands, agents. Install with npx and go.

Standing on the Shoulders of Giants

Legion didn't emerge from the void. It cherry-picked the best patterns from proven orchestration systems, combined them into something greater than the sum of its parts, and left behind the complexity that made each hard to adopt.

Agency Agents

Took: The 52 specialist personalities (51 inherited + 1 Legion-native) — 85–348 line character sheets with deep expertise, communication styles, hard rules, and personality quirks across 9 divisions. The foundation everything else stands on.

Left behind: Original "Agency" branding and namespace

GSD (Get Shit Done)

Took: Adaptive questioning flow (vision → requirements → constraints), orchestrator/subagent split, human-readable .planning/ state management.

Left behind: 33+ workflow files, custom CLI tooling, complex config

Conductor

Took: Build → review → fix evaluate-loop, quality gates, parallel dispatch pattern, typed evaluators for different work.

Left behind: Board-of-directors governance, message bus IPC, 50+ iteration limits

Shipyard

Took: Wave-based execution, max 3 tasks per plan constraint, atomic commits per completed plan.

Left behind: 29 commands, checkpoint/rollback system, complex hook infrastructure

Best Practice Config

Took: Plugin architecture (commands → skills → agents), agent frontmatter schema, structured metadata for programmatic catalog.

Left behind: RPI workflow, custom hooks infrastructure

Daem0n-MCP

Took: Semantic memory architecture — store, recall, decay primitives. Compute decay at recall time, not destructively. Full history always preserved.

Left behind: Hook-driven architecture, MCP server dependency

Feature-dev

Took: Confidence-based review filtering (80%+), competing architecture designs (2–3 approaches), 3-agent model.

Left behind: No state persistence, no memory, no quick mode

code-foundations

Took: Anti-rationalization tables, evidence-backed checklists, scope discipline.

Left behind: 614-check pipeline, heavy token consumption

beads

Took: Git-native state, ready primitive, semantic compaction, actor-based audit trails.

Left behind: Scope creep, MEOW naming, $100+/hour cost

Auto-Claude

Took: Worktree isolation, multi-stage spec pipeline, semantic merge, dynamic security profiles.

Left behind: 1,751 files, Python-Electron split, 50-iteration QA

bjarne

Took: Verification points, stale loop detection, environment auto-remediation, verbose output redirection.

Left behind: 2,500 lines of Bash, zero tests

Puzld.ai

Took: DPO preference extraction, debate-with-winner-tracking, clean adapter pattern.

Left behind: Near-zero test coverage, 95 releases in 3 months

The Tithe

The Legion asks not for blood, but for sustenance.
Those who have commanded the many and found them worthy
may offer tribute, that the voices may continue to serve.

Make an Offering

Your sacrifice sustains the many.