Skip to main content

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.

VBW transforms Claude Code from a conversational coding assistant into a complete development lifecycle engine. You describe what you want to build. VBW breaks it into phases, spawns specialized agent teams to plan and write the code, verifies every commit, and persists state across sessions — all with dramatically lower token overhead than running agent teams manually.

Installation

Install VBW in two commands inside Claude Code. No manual setup required.

Quickstart

Go from zero to your first completed phase in under 10 minutes.

How It Works

Understand the phase → plan → task → commit lifecycle and how agents coordinate.

Command Reference

All 24 commands documented with flags, defaults, and real examples.

Why VBW

Most Claude Code workflows rely on spawning subagents that report back and die. VBW is designed from the ground up for Opus 4.6+ platform features — Agent Teams with real parallelism, native hooks for continuous verification, and platform-enforced tool permissions that can’t be bypassed during context compaction.
CategoryStock Agent TeamsVBWSaving
Base context overhead10,800 tokens1,500 tokens86%
Agent coordination (×4 agents)16,000 tokens1,200 tokens93%
Context duplication16,500 tokens900 tokens95%
Total coordination overhead87,100 tokens12,100 tokens86%

The two commands you need

/vbw:init
Run once per project. Sets up your environment, scaffolds .vbw-planning/, configures Agent Teams and the statusline, and installs git hooks. For existing codebases, maps the codebase with 4 parallel Scout agents before auto-chaining to /vbw:vibe.
/vbw:vibe
The one command. Auto-detects project state and does the right thing: scopes requirements, creates a phased roadmap, plans the next phase, executes it with parallel Dev agents, runs QA verification, and loops until you’re done. Run it repeatedly — state persists in .vbw-planning/ across sessions.

What’s included

7 Specialized Agents

Scout, Architect, Lead, Dev, QA, Debugger, and Docs — each with platform-enforced tool permissions.

24 Commands

Full lifecycle coverage from init through archive, with monitoring, debugging, and maintenance commands.

22 Hook Handlers

Continuous verification across 11 event types — security, validation, and lifecycle management.

Database Safety Guard

Blocks 40+ destructive patterns across every major ORM before they reach the shell.

Skills.sh Integration

Auto-detects your tech stack and installs community skills from the open registry.

Worktree Isolation

Each Dev agent gets its own git worktree — physical filesystem isolation for parallel work.
VBW requires macOS or Linux. Windows is not supported natively — run Claude Code inside WSL if you’re on Windows.

Build docs developers (and LLMs) love