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.

Lifecycle commands own the main loop: setting up your environment and driving the full plan-execute-verify cycle from a single entry point.

/vbw:init

Set up your VBW environment, scaffold .vbw-planning/, and configure everything you need to start building.
/vbw:init
What it does:
  • Configures Agent Teams and the VBW statusline in settings.json
  • Scaffolds .vbw-planning/ with templates and config.json
  • Auto-installs git hooks (pre-push version enforcement)
  • Detects your stack and suggests community skills from skills.sh
For existing codebases, init runs the full brownfield onboarding flow: it maps your codebase with /vbw:map (using Scout teammates), uses those results to inform stack detection and skill suggestions, and then chains directly into /vbw:vibe to start planning.
Run /vbw:init once per project. If VBW is already initialized, use /vbw:config to change settings or /vbw:vibe to continue building.

/vbw:vibe

The one command. Auto-detects your project state, parses natural language intent, or accepts explicit flags.
/vbw:vibe [intent or flags]

How it works

/vbw:vibe reads your .vbw-planning/ directory and routes to the right mode automatically. You don’t need to tell it what to do — it already knows where you are.

13 modes

Walks you through project setup: name, purpose, requirements, and initial phase decomposition. Runs domain research and a calibrated discovery discussion before generating PROJECT.md, REQUIREMENTS.md, ROADMAP.md, and STATE.md.
Decomposes your project into 3–5 independently plannable phases. Writes ROADMAP.md and creates phase directories.
Runs the unified discussion engine. Auto-calibrates between Builder mode (fast, pragmatic) and Architect mode (thorough, pattern-focused) based on conversation signals. Captures decisions to {phase}-CONTEXT.md.
Generates 5–10 assumptions by impact category (scope, technical, ordering, dependency, user preference) and gathers your feedback before any planning begins.
When a phase has status: issues_found in its UAT report, plain /vbw:vibe loads that report and continues remediation automatically. Major/critical issues chain discuss → plan → execute. Minor-only issues use quick-fix remediation.
Scans archived milestones deterministically (including legacy milestones missing SHIPPED.md) and surfaces unresolved UAT issues for recovery across all affected phases.
Generates detailed execution plans for the current phase. Breaks work into tasks, maps dependencies, and writes {NN}-PLAN.md files.
Executes the current phase plan using the Lead + Dev agent team. Commits work, runs QA, and writes SUMMARY.md on completion.
Appends a new phase to ROADMAP.md and creates its phase directory.
Inserts a new phase before an existing one and renumbers downstream phases.
Removes a phase from the roadmap and cleans up its directory.
Runs a 7-point audit, enforces a UAT gate (unresolved UAT issues block archiving regardless of --skip-audit), then archives the milestone with a SHIPPED.md.

Flags

FlagDescription
--planForce planning mode
--executeForce execution mode
--discussForce discussion mode
--assumptionsSurface key assumptions for the current phase
--scopeForce scope mode
--add "description"Add a new phase with the given description
--insert N "description"Insert a new phase before phase N
--remove NRemove phase N
--archiveForce archive mode
--yoloSkip all confirmation gates and auto-loop remaining phases
--effort=<level>Override effort profile: thorough, balanced, fast, or turbo
--skip-qaSkip QA verification step
--skip-auditSkip non-UAT pre-archive audit checks (UAT gate still enforced)
Phase numbers are optional for most flags — VBW auto-detects the current phase when you omit them.

Examples

/vbw:vibe
/vbw:vibe --plan 3 --effort=turbo
/vbw:vibe --execute
/vbw:vibe --archive
/vbw:vibe Build me a REST API with authentication
Natural language intent works with /vbw:vibe. Keywords like “build”, “plan”, “discuss”, “wrap up”, or “add a new phase for X” are parsed and routed to the right mode automatically. VBW confirms its interpretation before executing.

Build docs developers (and LLMs) love