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.
Monitoring commands give you visibility into what’s been built and confidence that it meets the spec. Use them on demand — VBW also runs QA automatically via hooks during builds.
/vbw:status
Display a full project progress dashboard.
What you get:
- All phases with completion bars and current status
- Velocity metrics (plans complete, phases shipped)
- Suggested next action
Flags:
| Flag | Description |
|---|
--metrics | Add token consumption breakdown per agent |
/vbw:qa [phase]
Run deep verification on a completed phase.
/vbw:qa [phase-number] [--tier=quick|standard|deep] [--effort=level]
QA tiers
| Tier | Checks | When to use |
|---|
| Quick | 5–10 | Fast sanity check after minor changes |
| Standard | 15–25 | Routine phase verification |
| Deep | 30+ | Pre-archive or high-stakes verification |
thorough → deep, fast/turbo → quick). Override with --tier.
How it works
/vbw:qa uses a goal-backward methodology: it starts from the phase’s acceptance criteria and works backward to verify that each requirement is met by the implementation. This catches gaps that forward-reading checks miss.
Phase auto-detection: When you omit the phase number, VBW targets the most recently completed phase.
Output: Produces {NN}-VERIFICATION.md in the phase directory with pass/fail results per check.
Continuous QA: Hooks run QA automatically during builds. Use /vbw:qa when you want thorough, on-demand verification — for example, before accepting a phase or before archiving.
Flags:
| Flag | Description |
|---|
--tier=quick|standard|deep | Override the verification tier |
--effort=level | Override effort profile for this run |
/vbw:verify [phase]
Run human acceptance testing for a phase.
/vbw:verify [phase-number]
How it works
/vbw:verify presents each success criterion from the phase spec one at a time and prompts you — the human — to evaluate it. This is UAT, not automated testing.
For each criterion you provide a verdict:
pass — criterion metfail — criterion not met (with notes)partial — criterion partially met (with notes)
Interruption recovery: If you stop mid-way through verification, /vbw:verify resumes from the last unevaluated criterion on the next run.
Output: Produces {NN}-UAT.md with your verdicts. If any issues are found, /vbw:vibe will automatically route to UAT remediation on the next run.
Phase auto-detection: When you omit the phase number, VBW targets the phase awaiting verification.
Example:
/vbw:verify runs UAT inline in your conversation via prompts — it does not spawn a QA agent. Your judgment is the acceptance gate.