maxi-superpowers
A spec-driven development plugin for Claude Code, OpenCode, and Antigravity (legacy Gemini CLI also supported). maxi turns "build me X" into a disciplined pipeline — constitution → spec → clarify → plan → tasks → analyze → implement — and gates each phase so nothing ships without the design artifacts to back it. Under the hood it delegates implementation to superpowers (TDD, subagents, code review).
Why maxi?
- Design before code — every feature gets a written spec, plan, and task list, not just a prompt and a diff.
- Phase gating — skills refuse to run out of order, so you can't skip clarification and discover the gap at implementation time.
- Decisions are recorded — architectural choices become ADRs automatically (with your consent), so the why survives.
- Greenfield or brownfield — start a fresh project, or reverse-engineer an existing codebase into spec baselines.
Installation
For Claude Code
# From the plugin marketplace (plugin name: maxi):
claude plugin install maxi
# Or install locally:
git clone https://github.com/amoutiers/maxi-superpowers
cd maxi-superpowers
claude plugin install .
For Antigravity CLI
# Install locally:
git clone https://github.com/amoutiers/maxi-superpowers
cd maxi-superpowers
agy plugin install .
# Or import your legacy Gemini extensions:
agy plugin import gemini
For OpenCode
Add to your opencode.json:
{
"plugin": ["maxi-superpowers@git+https://github.com/amoutiers/maxi-superpowers.git"]
}
Then restart OpenCode. See .opencode/INSTALL.md for details.
For Legacy Gemini CLI (deprecated — use Antigravity)
# Install from the GitHub repository:
gemini extensions install https://github.com/amoutiers/maxi-superpowers
# Or install locally:
git clone https://github.com/amoutiers/maxi-superpowers
cd maxi-superpowers
gemini extensions install .
Start here
- New project? Follow the Quick Start below —
/maxi:constitution, then /maxi:specify <feature>.
- Existing codebase? Jump to Onboarding an existing project — migrate your spec-kit specs, or reverse-engineer your code into spec baselines.
You don't have to memorize commands: describe what you want and maxi routes you to the right skill, or type the /maxi:* command explicitly. A constitution is required before the pipeline and the brownfield/ADR migrations, so run /maxi:constitution first — with one exception: spec-kit migrants run /maxi:migrate-from-speckit, which brings their existing constitution over.
Quick Start
Your first feature, end to end:
/maxi:constitution # one-time: establish your project's principles
/maxi:specify add email + password login # start a spec via guided Q&A (→ specified)
/maxi:clarify # answer any open questions (→ clarified)
/maxi:plan # technical plan + ADR proposals (→ planned)
/maxi:tasks # checkbox task list (→ tasked)
/maxi:analyze # 7-pass quality audit (→ analyzed)
/maxi:implement # TDD execution + code review (→ done)
Each command reads the previous artifacts and refuses to run if the spec is in the wrong phase — so the path is hard to get wrong. Artifacts land in docs/maxi/ (see Artifact Structure).
Pipeline Commands
Full reference for the forward pipeline:
| Command | Description |
|---|
/maxi:constitution | Establish or amend project principles — required before any other command |
/maxi:specify | Create a new feature spec via guided design dialogue |
/maxi:clarify | Resolve open questions in a spec before planning |
/maxi:plan | Generate a technical implementation plan from the spec |
/maxi:tasks | Extract a structured checkbox task list from the plan |
/maxi:analyze | Run a 7-pass quality audit across all artifacts (includes ADR alignment) |
/maxi:implement | Execute the task list and transition the spec to done |
Beyond the forward pipeline there are lifecycle commands (/maxi:board, /maxi:park, /maxi:resume, /maxi:cancel, /maxi:revise) and the migration utilities covered under Onboarding an existing project.
Artifact Structure
