Lifecycle commands own the main loop: setting up your environment and driving the full plan-execute-verify cycle from a single entry point.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:init
Set up your VBW environment, scaffold .vbw-planning/, and configure everything you need to start building.
- Configures Agent Teams and the VBW statusline in
settings.json - Scaffolds
.vbw-planning/with templates andconfig.json - Auto-installs git hooks (pre-push version enforcement)
- Detects your stack and suggests community skills from skills.sh
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.
/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.
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
bootstrap — no project defined yet
bootstrap — no project defined yet
PROJECT.md, REQUIREMENTS.md, ROADMAP.md, and STATE.md.scope — project defined, no phases yet
scope — project defined, no phases yet
ROADMAP.md and creates phase directories.discuss — exploration before planning
discuss — exploration before planning
{phase}-CONTEXT.md.assumptions — surface key assumptions
assumptions — surface key assumptions
UAT remediation — unresolved UAT issues
UAT remediation — unresolved UAT issues
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.milestone UAT recovery — archived milestones with open issues
milestone UAT recovery — archived milestones with open issues
SHIPPED.md) and surfaces unresolved UAT issues for recovery across all affected phases.plan — create execution plans
plan — create execution plans
{NN}-PLAN.md files.execute — build the phase
execute — build the phase
SUMMARY.md on completion.add phase — add a new phase at the end
add phase — add a new phase at the end
ROADMAP.md and creates its phase directory.insert phase — insert a phase at a specific position
insert phase — insert a phase at a specific position
remove phase — remove an existing phase
remove phase — remove an existing phase
archive — wrap up the project
archive — wrap up the project
--skip-audit), then archives the milestone with a SHIPPED.md.Flags
| Flag | Description |
|---|---|
--plan | Force planning mode |
--execute | Force execution mode |
--discuss | Force discussion mode |
--assumptions | Surface key assumptions for the current phase |
--scope | Force scope mode |
--add "description" | Add a new phase with the given description |
--insert N "description" | Insert a new phase before phase N |
--remove N | Remove phase N |
--archive | Force archive mode |
--yolo | Skip all confirmation gates and auto-loop remaining phases |
--effort=<level> | Override effort profile: thorough, balanced, fast, or turbo |
--skip-qa | Skip QA verification step |
--skip-audit | Skip non-UAT pre-archive audit checks (UAT gate still enforced) |