Getting Started
Prerequisites
- Node.js 20+ -- check with
node --version - Anthropic API key -- get one at platform.claude.com
Set your API key:
export ANTHROPIC_API_KEY="sk-ant-..."Or use claude login if you have Claude Code installed.
Install
npm install -g vibe-racerVerify the installation:
vibe-racer --version
# 0.2.0Your First Race
1. Initialize your project
Navigate to any project directory and run:
cd your-project
vibe-racer initThis creates:
.vibe-racer.yml-- configuration fileplans/-- directory for task plan documents
2. Create a task
vibe-racer new "Add user authentication"This creates plans/0001_add-user-authentication/ with:
state.yml-- pipeline state tracker00_objective.md-- your objective template
3. Write your objective
Open plans/0001_add-user-authentication/00_objective.md and describe what you want to build. Be as detailed or as brief as you like -- the race engineer will ask clarifying questions.
Then tick the checkbox at the bottom:
- [x] Ready to advance to Objective Review4. Drive the first lap
vibe-racer driveThe race engineer picks up your task, reads the objective, and generates product-scoping questions in 01_product_questions.md. Each question includes the race engineer's recommended answer pre-filled.
5. Review at the pit stop and iterate
Open the questions file. Read each answer. Edit only what you disagree with. Then tick the checkbox at the bottom and drive again:
vibe-racer driveRepeat this cycle through all 5 laps:
Lap 1: Objective -> Lap 2: Product -> Lap 3: Design -> Lap 4: Plan -> Lap 5: Execute6. Check the pit wall
At any point, see where your tasks stand:
vibe-racer pitwallWhat Happens at Each Lap
| Lap | You do | Race engineer does |
|---|---|---|
| Objective | Write what you want to build | Reviews, asks product questions |
| Product | Review/edit pre-filled answers | Writes product spec, asks design questions |
| Design | Review/edit pre-filled answers | Writes design spec, asks plan questions |
| Plan | Review/edit pre-filled answers | Writes implementation plan + execution playbook |
| Execute | Review the plan, tick the checkbox | Implements code milestone by milestone |
Tips
- You don't need to fill everything in -- the race engineer pre-fills recommended answers. Only edit disagreements.
- If the race engineer needs more info, it will radio back with follow-up questions and uncheck the checkbox. Answer them and re-tick.
- Small tasks? The race engineer can flag them as trivial during objective review, skipping product and design laps.
- Need to discuss? Use
vibe-racer radioto open an interactive session with the race engineer at a pit stop.

