Quick start
Open your coding agent with terminal access. Copy this prompt to install 2build for that agent.
Install 2build for the coding agent I am using. Follow
https://raw.githubusercontent.com/2found/2build/main/docs/install.md. Detect my OS and
current agent, reuse a working bbs installation or install the CLI, then install the
skill pack for this agent only. Verify bbs --version and the installed skills; report
any missing prerequisite instead of claiming success. Tell me whether I need to restart
and give me the exact Autopilot invocation for my agent to run my first small task.Get ready
You need a supported coding agent and its existing model access. Claude Code and Codex need their CLI on PATH. Your normal agent usage charges apply. No separate 2build model account or Orca is needed for Autopilot.
The agent installs or reuses the bbs CLI, installs its own skill pack and verifies both. Restart when it asks you to. If a prerequisite is missing, it should name it rather than claim success.
Use Homebrew or a verified release archive on macOS/Linux; use WSL on Windows. Installation and troubleshooting covers the manual paths and compatible agents.
First ticket
Open a Git repo with usable checks. Choose the session model and one small task with a clear success check. Autopilot works on your current checkout and leaves the change uncommitted for you to review and save; create your preferred branch first if you want isolation.
Invoke the skill in your agent chat. Replace the example with your own task. Add --stop-after=plan to this first request to stop at the plan/prototype review checkpoint.
| Agent | First invocation |
|---|---|
| Claude Code / Grok | /bbs:autopilot "Fix one bug. Show the plan first, then implement, review and QA." |
| Codex | $bbs:autopilot "Fix one bug. Show the plan first, then implement, review and QA." |
| OMP | /autopilot "Fix one bug. Show the plan first, then implement, review and QA." |
| Antigravity / compatible agents | Ask it to use the installed Autopilot skill for your task. |
Review the plan and, for UI work, open the prototype. Adjust the scope or flow now. Autopilot never asks you to paste a /goal block; it keeps going on its own until it is done or blocked. With --stop-after=plan, follow its resume instruction to continue.
Autopilot implements, reviews, repairs and runs project checks and QA. A passing handoff leaves the change uncommitted in your checkout, with evidence, for you to save; a blocker names the missing input. DONE does not publish or deploy. You still choose the release step.
After a restart, give Autopilot the ticket ID to resume. Keep credentials in a private local file or secret store; share the reference, never values in chat.
No project yet?
Open an empty folder in your agent and give Autopilot your idea in one sentence, or none and it asks a few questions and proposes three.
| Agent | Start a new project |
|---|---|
| Claude Code / Grok | /bbs:autopilot "<your idea in one sentence>" |
| Codex | $bbs:autopilot "<your idea in one sentence>" |
Autopilot interviews you, writes docs/REQUIREMENT.md and builds a clickable prototype. You approve it or ask for changes once. It then chooses a minimal architecture, creates the services from 2build starters, makes the product run locally with one command, prepares deploy configuration, runs the harness, review and QA, and saves the project skeleton as one commit. It creates no VM, domain, account or deploy; those wait for your first /bbs:release.
The result is docs/BACKLOG.md: a list of features where each item is a paste-ready /bbs:autopilot "..." line. Paste the first one to build it; Autopilot ticks the item and names the next. The starter guide lists the templates (bbs bootstrap and bbs starter check require CLI 1.95.0+).
Choose the next workflow
Use a focused skill for planning, debugging, review or copy. Foreman uses Orca for larger projects with dependent tickets and supervised workers. It has a separate project plan/design review and finish policy. Reference docs are in English.
