npx maxsimcli@latest

The Problem in 30 Seconds

You start a session with Claude. The first 20 minutes are great. Then it starts forgetting your architecture decisions. It repeats the same mistakes. Output quality drops. You start a new session and lose all context.

This is context rot — and it gets worse the bigger your project is.

MAXSIM fixes this by breaking your build into phases, planning each one independently, and running each task in a fresh subagent with only the context it needs. No rot. No drift. Consistent quality from phase 1 to phase 50.

Try It in 1 Minute

# Install
npx maxsimcli@latest

# In Claude Code, start a new project:
/maxsim:new-project

# Or jump straight to planning a phase:
/maxsim:plan-phase 1

# Execute it:
/maxsim:execute-phase 1

That's the loop. Discuss → Plan → Execute → Verify. Each phase is isolated, each task gets a fresh agent, every change gets an atomic commit.

Who Is This For

Individual developers who want to ship complex projects with Claude without losing coherence over long sessions.

Teams who want a shared structure for AI-assisted development — consistent planning, traceable decisions, reproducible phases.

AI-heavy projects (SaaS, CLIs, data pipelines) where a single Claude session can't hold the full project context.

Not a fit if your project is a single file, a one-shot script, or you just want quick answers from Claude — MAXSIM is a workflow system, not a chat interface.

How It Works

MAXSIM installs 30+ slash commands into your AI runtime. Each command is a structured workflow that spawns specialized subagents with fresh context.

The Core Loop

1. Initialize your project

/maxsim:new-project

Answer a few questions → MAXSIM researches your domain, scopes v1/v2, and creates a phased roadmap in .planning/.

2. Discuss a phase (optional but recommended)

/maxsim:discuss-phase 1

Shape the implementation before anything gets built. Surfaces gray areas and locks in decisions.

3. Plan the phase

/maxsim:plan-phase 1

Research agent investigates. Planner creates atomic task plans. Plan-checker verifies them. You get a PLAN.md ready to execute.

4. Execute

/maxsim:execute-phase 1

Plans run in parallel waves. Each task gets its own fresh executor agent and atomic git commit. Verifier checks the codebase delivered what the phase promised.

5. Verify

/maxsim:verify-work 1

Walk through testable deliverables. Broken things get fix plans automatically.

6. Repeat until shipped

/maxsim:complete-milestone
/maxsim:new-milestone

Real-World CLI Flow

You: /maxsim:new-project
MAXSIM: Tell me about your project...
You: A CLI tool that converts PDFs to structured JSON using AI
MAXSIM: [spawns 4 research agents in parallel]
        [synthesizes findings]
        [creates REQUIREMENTS.md and ROADMAP.md with 8 phases]
        Phase 1: PDF parsing + text extraction
        Phase 2: AI-powered structure detection
        ...

You: /maxsim:plan-phase 1
MAXSIM: [research agent investigates pdf libraries]
        [planner creates 3 atomic task plans]
        [plan-checker verifies feasibility]
        Ready. Run /maxsim:execute-phase 1

You: /maxsim:execute-phase 1
MAXSIM: [wave 1: executor installs dependencies, commits]
        [wave 2: executor implements PDF reader, commits]
        [wave 3: executor adds tests, commits]
        [verifier confirms phase goal achieved]
        ✓ Phase 1 complete. 3 commits. Dashboard updated.

Live Dashboard

npx maxsimcli dashboard

Real-time web dashboard — bundled inside the CLI, no separate setup needed.

• Phase overview — progress bars, milestone stats, completion percentage
• Phase drill-down — expand phases to see individual tasks with checkboxes
• Inline Markdown editor — edit plan files directly in the browser (CodeMirror, Ctrl+S)
• Todos & Blockers — manage todos and resolve blockers from STATE.md
• Auto-launches during /maxsim:execute-phase so you always have a live view
• LAN sharing — share with teammates on the same network

npx maxsimcli dashboard --network  # LAN sharing + QR code

Commands

Core Workflow

Navigation & Utilities

Phase Management

Milestone & Quality

Todos

Live Dashboard

Settings

Installation

npx maxsimcli@latest

The installer prompts you to choose:

1. Runtime — Claude Code, OpenCode, Gemini, Codex, or all
2. Location — Global (all projects) or local (current project only)

Verify with:

• Claude Code / Gemini: /maxsim:help
• OpenCode: /maxsim-help
• Codex: $maxsim-help

npx maxsimcli --claude --global    # Claude Code → ~/.claude/
npx maxsimcli --opencode --global  # OpenCode → ~/.config/opencode/
npx maxsimcli --gemini --global    # Gemini CLI → ~/.gemini/
npx maxsimcli --codex --global     # Codex → ~/.codex/
npx maxsimcli --all --global       # All runtimes

Configuration

Project settings live in .planning/config.json, created during /maxsim:new-project or editable via /maxsim:settings.

{
  "model_profile": "balanced",
  "branching_strategy": "none",
  "commit_docs": true,
  "research": true,
  "plan_checker": true,
  "verifier": true,
  "parallelization": true,
  "brave_search": false
}

Model Profiles

MAXSIM has 4 model profiles that control which Claude model each of the 11 specialized agents uses:

tokenburner assigns Opus to every single agent. Use it when cost is no concern and you want maximum quality end-to-end.

Switch profiles at any time:

/maxsim:set-profile quality
/maxsim:set-profile balanced
/maxsim:set-profile budget
/maxsim:set-profile tokenburner

You can also override individual agents in config.json:

{
  "model_profile": "balanced",
  "model_overrides": {
    "maxsim-planner": "opus",
    "maxsim-executor": "opus"
  }
}

Hook System

MAXSIM installs three compiled hooks into Claude Code:

The context bar shows a 10-segment indicator that turns red and blinks above 95% — your signal to spawn a new session before quality degrades.

Agents

11 specialized subagents, each with fresh context and a single responsibility:

Contributing

MAXSIM is open source and contributions are welcome.

• Bug reports: Open an issue
• Feature requests: Start a discussion
• PRs: Fork, branch, and open a pull request — see CLAUDE.md for architecture overview

The "runtime" for MAXSIM is the AI itself — commands are markdown prompts in templates/, not compiled code. If you want to improve a workflow or add a command, you're editing markdown.

Acknowledgments

Inspired by GSD (Get Shit Done).

License

MIT License. See LICENSE for details.