Appearance
wb-flow Documentation
The official documentation for the 33-command
/wb*agentic workflow system.This is a field manual — opinionated, direct, and written for developers who actually use these commands rather than just read about them.

Who is this for?
Stack-agnostic. wb-flow runs on any project where you have source files and markdown — Vue, React, Svelte, Solid, Next.js, Nuxt, Astro, Django, FastAPI, Rails, Go, Rust, anything. The 33 commands operate on package.json, source trees, and report folders; none of them care which framework wrote the code they're reading.
The one exception: /wbToWBC converts code to use the wbc-ui2 component primitives, which are Vue-based. If you're not on Vue, ignore that one command. The other 32 are universal.
Why examples skew Vue. This documentation was authored within a Vue monorepo (wb-core, wb-press, wbdataviewer2.wbc-ui.com), so every worked example draws from there. The patterns transfer one-for-one — /wbAudit reads source code the same way whether the source is .vue, .tsx, or .py.
What you need on day one:
- A folder with code in it (any language)
- A way to run the commands (any AI agent environment that accepts prompts)
- Nothing else — no Node version requirement, no framework lock-in
How outputs are tagged (v1.8+)
Every output file from a suggestion-emitting command (/wbPlan, /wbAudit, /wbReview, /wbVision, /wbIdea, /wbStandup, /wbNext, /wbActOn) carries three metadata layers:
1. YAML front-matter:
yaml
---
type: 🔨 Worker # the dominant action type
emits: mixed # `pure` or `mixed`
---2. A Requires column in every recommendation table:
| # | Requires | Suggestion | … |
|---|---|---|---|
| 1 | 🔨 Worker | Refactor bin/install.js | … |
| 2 | ✅ Validator | Audit the new auth middleware | … |
| 3 | 📋 Mechanical | Run npm pack --dry-run | … |
3. The four canonical action types:
- 🧠 Planner — Deep reasoning, strategy, multi-step decomposition
- ✅ Validator — Big-thinker code-quality judgment, scoring
- 🔨 Worker — Coder/executor: surgical code edits, refactors
- 📋 Mechanical — Run command, parse output, format report. No judgment
See concepts/model_recommendations for which model to use per role.
How to read this documentation
| Folder | When to read it |
|---|---|
start_here/ | First time using the system, or returning after weeks away |
concepts/ | When you want to understand why the system works the way it does |
daily_use/ | When you've forgotten which command to run at 10am vs. 4pm |
commands/ | Per-command deep-dives — seven reading files per command |
session_lifecycle/ | When and how to start and stop AI sessions cleanly |
The seven files per command:
| File | Length | Read when |
|---|---|---|
hub (wbX.md) | 1 page | Quick overview: purpose, invocation, what happens |
| eli5 | 1–2 paragraphs | One-line mental model |
| practical | 1 page | About to run the command, need trade-offs |
| expert | 2–3 pages | Considering modifying the template |
| examples | 3–5 pages | Forgot what the output looks like |
| exhaustive | 4–6 pages | Need the definitive edge-case simulation |
| live_demo | 2–4 pages | Want the command grounded in an actual workspace |
Reading order for a new user
start_here/installation— NPM, NPX, or Git installationstart_here/getting_started— 30-day onboarding planstart_here/first_run_walkthrough— Annotated first sessionstart_here/bootstrapping_existing_project— Inheriting code without/wbSetupconcepts/overview_agentic_workflows— Commands grouped by the question they answerdaily_use/the_daily_playbook— Morning → midday → afternoon → evening shapecommands/— Pick the command you're about to use; read itspracticalfile
If you only ever read one of these, read the daily playbook.
Concept deep-dives
Cross-cutting ideas that don't belong in any single command's docs:
concepts/agentic_vs_manual— When structured commands beat freeform prompting (and when they don't)concepts/command_classification— All 33 commands grouped into functional familiesconcepts/command_composition— Self-application, chaining notation, chain recipesconcepts/wbPlan_flag— How--actand--wbPlancompose across commandsconcepts/plan_state_management— The five task states (⬜✅⏸️🚫🔄) and override flagsconcepts/ideas_pipeline— The 8-step Ideas Pipeline from birth to executionconcepts/model_recommendations— Which model to use per command roleconcepts/flags_and_shortcuts— System-wide flag→shortcut grammarconcepts/universal_flags_exhaustive_simulation— Brain Control super-flags simulationconcepts/wbWorkflow/README— Workflow architecture, lifecycle, and task sequencingsession_lifecycle/README— Golden Save Point, session boundaries, publishing arcs
The 33-command catalog
Grouped by the question you're asking when you reach for them.
"What is this codebase?" — Context Builders
| # | Command | Purpose | Hub |
|---|---|---|---|
| 01 | /wbSetup | Write context.md + dev.md for a new package | hub |
| 02 | /wbContext | Refresh package context against current code | hub |
| 03 | /wbStandup | Monorepo-wide scan: what's in-flight, what's stale | hub |
"What should I do next?" — Planners
| # | Command | Purpose | Hub |
|---|---|---|---|
| 04 | /wbPlan | Break a goal into a worker/validator task table | hub |
| 05 | /wbVision | Brainstorm features when the queue is empty | hub |
| 06 | /wbIdea | Capture and score speculative ideas | hub |
| 07 | /wbNext | Pick the next optimal command based on repo state | hub |
| 08 | /wbHelp | Print the command catalog or per-command help | hub |
| 09 | /wbActOn | Triage a diagnostic doc into ranked actions | hub |
| 10 | /wbExplain | Generate a persistent explanation of code or a task | hub |
"Execute and validate" — Workers & Validators
| # | Command | Purpose | Hub |
|---|---|---|---|
| 11 | /wbWork | Execute tasks defined in a plan file | hub |
| 12 | /wbValid | Audit /wbWork output against the plan — PASS/FAIL | hub |
"Is this any good?" — Critics
| # | Command | Purpose | Hub |
|---|---|---|---|
| 13 | /wbAudit | Brutal review against production standards | hub |
| 14 | /wbReview | PR-style review of a change vs. its plan | hub |
| 15 | /wbTest | Run tests, classify failures | hub |
| 16 | /wbCheck | Pre-flight quiz to verify AI understanding | hub |
"Clean this up" — Surgeons
| # | Command | Purpose | Hub |
|---|---|---|---|
| 17 | /wbClean | Find dead code, stale files, forgotten console.log | hub |
| 18 | /wbRefactor | Restructure code without changing behavior | hub |
| 19 | /wbDebug | Hypothesize then investigate a specific error | hub |
| 20 | /wbDoc | Generate JSDoc + READMEs from code | hub |
"Ship it" — Shippers
| # | Command | Purpose | Hub |
|---|---|---|---|
| 21 | /wbRelease | Bump versions, unpick workspace:* | hub |
| 22 | /wbPublish | Build + push a package to npm | hub |
| 23 | /wbDeploy | Build + push an app to a web host | hub |
| 24 | /wbLicense | Inject premium gating and license checks | hub |
| 25 | /wbBroadcast | Generate release announcement kit | hub |
| 26 | /wbMonetize | Bootstrap Free/Pro/Dev tier plumbing | hub |
"Version control" — Archivist
| # | Command | Purpose | Hub |
|---|---|---|---|
| 27 | /wbGit | Analyze diff, draft Conventional Commit | hub |
| 28 | /wbLog | Append a quick log note to the session tracker | hub |
"Protect & cross-cut" — Security, Translation, Migration
| # | Command | Purpose | Hub |
|---|---|---|---|
| 29 | /wbSecure | Red-team scan: secrets, XSS, insecure deps | hub |
| 30 | /wbTranslate | Pull hardcoded strings to i18n keys | hub |
| 31 | /wbToWBC | Rewrite legacy/Vuetify into wbc-ui2 components | hub |
"Session telemetry" — Tracking
| # | Command | Purpose | Hub |
|---|---|---|---|
| 32 | /wbTrack | Toggle session-wide logging of /wb* invocations | hub |
| 33 | /wbStopTrack | Finalize session, archive tracker, prepare for closure | hub |
What this documentation is NOT
- Not the runtime templates. The source-of-truth
_template.mdfiles that define what each command actually does live inpackages/wb-flow/templates/commands/. This documentation covers how to use them. - Not API documentation. Every file is hand-authored for human readers.
- Not exhaustive on flags. If a command has 12 flags but only 3 matter daily, the docs cover the 3. The full flag list is in the runtime template.
wb-flow documentation — flow.wbc-ui.com · wb-flow on npm · wi-bg.com
