Documentation Index
Fetch the complete documentation index at: https://mintlify.com/swt-labs/vibe-better-with-claude-code-vbw/llms.txt
Use this file to discover all available pages before exploring further.
Starting a new project
Install VBW
If you haven’t installed VBW yet, follow the installation guide. You need Claude Code v1.0.33+ and Opus 4.6+.
Open your project directory in Claude Code
Navigate to your project directory and start Claude Code:Or use full auto mode if you prefer no interruptions:
Initialize VBW
Run VBW sets up your environment: scaffolds
/vbw:init once per project:.vbw-planning/, configures Agent Teams, installs git hooks, and detects your tech stack to suggest relevant skills from the Skills.sh registry. Answer any setup questions, then VBW auto-chains to /vbw:vibe.Describe your project
Run VBW detects no project is defined yet and asks about what you want to build. Describe your project. VBW gathers requirements and creates a phased roadmap stored in
/vbw:vibe with no arguments:.vbw-planning/ROADMAP.md.Plan the first phase
Run VBW detects phases are ready but not yet planned. The Lead agent researches your codebase, decomposes the first phase into plans and tasks, and assigns explicit file ownership to each plan. Each task maps to one atomic commit.
/vbw:vibe again:Execute the first phase
Run VBW detects plans are ready and enters Execute mode. The Lead agent spawns Dev teammates — one per plan. Dev agents work in parallel on their assigned tasks (implement → verify → commit), each in their own context window. The
/vbw:vibe again:file-guard.sh hook blocks any Dev from writing to files outside its declared ownership. When all Dev agents finish, QA runs automatically and produces VERIFICATION.md.Repeat for each phase, then archive
Keep running VBW runs a completion audit, archives state to
/vbw:vibe for each subsequent phase. State persists in .vbw-planning/ across sessions, so you can close your terminal and pick up exactly where you left off.When all phases are built:.vbw-planning/milestones/, and tags the git release.Picking up an existing codebase
The flow is identical, with one difference during/vbw:init.
/vbw:map with 4 Scout teammates in parallel to analyze your code across tech stack, architecture, quality, and concerns. Skill suggestions are based on what’s actually in your codebase. Then /vbw:vibe runs automatically with full codebase awareness.
From there, the same loop applies: /vbw:vibe until done, /vbw:vibe --archive.
Resuming a session
If you’ve closed your terminal or lost your session context, run:/vbw:resume reads ground truth directly from .vbw-planning/ — STATE.md, ROADMAP.md, PLAN.md, and SUMMARY.md files — without requiring a prior /vbw:pause. It detects interrupted builds, reconciles stale execution state, and tells you exactly what to do next.
Next steps
How it works
Understand the phase → plan → task → commit lifecycle and how agents coordinate.
Command reference
All 24 commands with flags, defaults, and examples.
Existing codebase guide
Detailed walkthrough of picking up a brownfield project with VBW.
Configuration
Tune effort profiles, autonomy levels, model routing, and concurrency controls.