 |
 |
English | 正體中文
The AI project lead for your terminal.
Claude Code writes the code. Autopilot plans it, delegates it, reviews it with a second engine, and remembers what it learned — so you ship without babysitting every step.
Distilled from 100+ completed AI-development projects.
# autopilot's optional pre-push hook:
❯ git push
[autopilot] completeness scan … ✗ TODO stub in auth.py:42
[autopilot] tests … ✗ 1 skipped (payment flow)
[autopilot] review … ⚠ unhandled error path
push blocked — fix it, or override with a reason
Claude Code is great at writing code. Autopilot makes it finish the job — the planning, checking, deciding, and remembering you'd otherwise do by hand:
- Hand it the goal, get back a result —
/l3/l4/l5/l6andceo-agentcan take a task end-to-end (sized, planned, built, reviewed, closed) and only stop to ask at the decisions that actually matter. - A second engine argues with your code — reviews can run on a different model family (GPT, Gemini), so more bugs get caught before your users see them instead of being rubber-stamped by the same model that wrote them.
- Catches the "done" that isn't — a no-stub/no-TODO scan, your tests, and a real code review, run in the quality gate before you merge (and in the optional pre-push hook above).
- Remembers, so your repo doesn't rot — captures the lessons, tracks the project, tells you what to do next, and adapts to your repo from a single markdown file in
.claude/.
It's a single Claude Code plugin — 27 skills, 3 methodology agents, 22 hooks, zero dependencies. It works fully on its own, and also plays nicely with the superpowers plugin if you have it.
This README was written by Claude and adversarially reviewed by GPT-5.5 and Gemini through Autopilot's own second-engine review flow.
New here? This page is the 5-minute tour. Everything deeper lives in Learn More.
dev-flow is the front door. It sizes the task and routes it — small things go straight through the gate, large things become a tracked project:
Without Autopilot, Claude starts grep-ing the codebase immediately — no plan, no phases, no quality gates. With it, the discipline is automatic.
/plugin marketplace add cookys/autopilot
/plugin install autopilot@autopilotThat's it. Now just talk to Claude — Autopilot's skills trigger on what you say:
You: "I'm starting on WebSocket compression" → sizes it, sets up a plan + branch + quality gates
You: "quick fix for the null check in auth" → fast path, still gated before commit
You: "what should I work on next?" → scans your projects and ranks them
You: "搞定這個重構，你決定" → full autonomous CEO mode
No commands to memorize — say it in your own words and the right skill steps in.
27 skills, grouped by what you're trying to do. Each one triggers from natural language — the Try saying lines are real triggers.
dev-flow (start here — sizes & routes the task) · quality-pipeline (test → scan → review) · finish-flow (clean closing sequence, nothing skipped).
Try saying: "let's implement X" · "quick fix for Y" · "is this ready to commit?"
survey (dual-agent industry research) · think-tank (6-role debate) · brainstorm (pre-code design exploration) · think-tank-dialectic (irreversible, high-stakes calls).
Try saying: "what do others use for X?" · "should we rewrite or patch?" · "要辯論一下"
ceo-agent (you set the goal, it executes) · /l3 /l4 /l5 /l6 (terse front-doors that pre-fill the CEO startup so one line ships the goal). They escalate where the work runs:
| Runs where | Reach for it when | |
|---|---|---|
/l3 |
inline, on this thread | full autonomy, but you want to watch it happen |
/l4 |
one background, worktree-isolated foreman | a long run you'd rather offload — your context stays clean, the authoritative quality verdict is held at depth 0 |
/l5 |
/l4, but the implementer is a different engine (agy / Gemini) |
cost-arbitrage, or a decorrelated second engine doing the mechanical coding |
/l6 |
/l5, plus verification authoring is delegated to a different engine |
when you want implementation and verification labor offloaded, while depth 0 keeps merge authority |
/l3 fix the flaky reconnect test, you decide # inline
/l4 ship the WebSocket reconnect system # offload to a background foreman
/l5 migrate the config loader to the new schema # foreman + heterogeneous implementer
/l6 ship the parser rewrite # hetero implementer + hetero verification authoring
Try saying: "CEO mode, handle it" · "全權處理" · "/l4 ship the reconnect system"
→ Per-level behaviour, presets, override flags (--expand / -x / --solo), and full examples: docs/skills.md.
Claude alone is enough. But point autopilot at a second engine family and its review/implement pipeline gets stronger — a cross-family qc panel catches what one vendor and its same-family reviewer jointly miss, and you get a heterogeneous implementer for cost-arbitrage. Recommended order: a subscription you already pay for ≻ a metered API key — OAuth-login runners (codex / agy / grok) need no token at all; GLM / MiniMax go in one canonical mode-600 file (~/.autopilot/endpoints.env) and are wired declaratively in .claude/review-loop-config.md.
Try saying: "set up a GLM reviewer" · "use MiniMax as the /l5 implementer"
→ Credential placement, the subscription-≻-API-key ladder, and the copy-paste setup: docs/installation.md.
learn (capture lessons) · retro (git-history retrospective) · next (what to do next) · distill (turn your repeated workflows into personal skills) · plus debug · profiling · test-strategy · audit · doc-sync.
Try saying: "record this for next time" · "回顧這週" · "what's the highest priority?"
→ Full catalog of all 27 skills, the three cognitive modes, and how they compose: docs/skills.md.
Claude Code (primary) — the two commands above. All 27 skills are available immediately as autopilot:dev-flow, autopilot:survey, etc.
Autopilot is portable: OpenCode discovers skills via .agents/skills/, Codex can use .agents/skills/ or the local package under platforms/codex/plugin whose manifest exposes skills with bundled support payload, Antigravity (agy) imports the repo as a Claude Code-source plugin, and there's a Windows + pre-commit-gate setup. Full per-platform instructions, plus the contributor dev-mode workflow, are in docs/installation.md.
The deep material, moved out of this page so it stays an onboarding tour:
| Topic | Doc |
|---|---|
| All 27 skills + three modes + how they compose | docs/skills.md |
| Superpowers coexistence — three scenarios, migration | docs/coexistence.md |
Per-project configuration — the .claude/ injection model |
docs/configuration.md |
| Installation & development — every platform, dev mode | docs/installation.md |
| Architecture & design — philosophy, methodology agents, credits | docs/architecture.md |
| Hooks — 22 runtime-enforcement hooks (tiers in the doc) | hooks/README.md |
| Changelog | CHANGELOG.md |
MIT — see LICENSE for details.