Appearance
Commands
Per-command deep-dives. 33 commands × 6 reading layers = the reference body of this documentation.
Each command lives in its own folder (wbSetup/, wbContext/, …, wbStopTrack/). Inside each folder you'll find up to seven files: a hub summary (wbX.md) and six layer files.
📋
Plan
Task table with costs + model assignments
/wbPlan
⚡
Work
Execute — edit files, run scripts, create reports
/wbWork
✅
Valid
Score work against acceptance criteria
/wbValid
FAIL →↻re-work
The seven files per command
| File | Length | Read when |
|---|---|---|
hub (wbX.md) | 1 page | You want a quick overview: purpose, invocation, what happens |
| eli5 | 1–2 paragraphs | You want a one-line mental model |
| practical | ~1 page | You're about to run the command and need the trade-offs |
| expert | 2–3 pages | You're considering modifying the command's runtime template |
| examples | 3–5 pages | You forgot what the command's output actually looks like |
| exhaustive_simulation | Full transcript | Complete behavior matrix for every input scenario |
| live_demo | Interactive | Real-time walkthrough of the command applied to an actual workspace |
Folder layout
commands/
├── wbSetup/ ─┐
├── wbContext/ │
├── wbPlan/ │ Each folder contains:
├── wbAudit/ │ <cmd>.md (hub summary)
├── wbReview/ │ <cmd>_eli5.md
├── ... │ <cmd>_practical.md
├── wbLog/ │ <cmd>_expert.md
├── wbStopTrack/ │ <cmd>_examples.md
├── wbTrack/ │ <cmd>_exhaustive_simulation.md
├── wbNext/ ─┘ <cmd>_live_demo.md
│
└── wb_commands_reference.json ← machine-readable command catalogQuick lookup — which command for which job?
| You want to... | Command | Folder |
|---|---|---|
Bootstrap a new package's context.md + dev.md | /wbSetup | wbSetup/ |
| Sync the AI's understanding of a package | /wbContext | wbContext/ |
| Monorepo-wide scan: what's in-flight? | /wbStandup | wbStandup/ |
| Break a goal into a worker/validator task plan | /wbPlan | wbPlan/ |
| Brainstorm features when the queue is empty | /wbVision | wbVision/ |
| Capture and score speculative ideas | /wbIdea | wbIdea/ |
| Pick the next optimal command based on repo state | /wbNext | wbNext/ |
| Print the command catalog or per-command help | /wbHelp | wbHelp/ |
| Triage a diagnostic doc into ranked actions | /wbActOn | wbActOn/ |
| Generate a persistent explanation of code or a task | /wbExplain | wbExplain/ |
| Execute tasks defined in a plan file | /wbWork | wbWork/ |
Validate /wbWork output against the plan | /wbValid | wbValid/ |
| Get a brutal review of code quality | /wbAudit | wbAudit/ |
| PR-style review of a specific change vs. its plan | /wbReview | wbReview/ |
| Run tests and triage failures | /wbTest | wbTest/ |
| Pre-flight quiz to verify the AI understands the code | /wbCheck | wbCheck/ |
Find dead code and forgotten console.log | /wbClean | wbClean/ |
| Restructure code without changing behavior | /wbRefactor | wbRefactor/ |
| Hypothesize then investigate an error | /wbDebug | wbDebug/ |
| Generate JSDoc + READMEs from code | /wbDoc | wbDoc/ |
Bump versions, unpick workspace:* | /wbRelease | wbRelease/ |
| Push a package to npm | /wbPublish | wbPublish/ |
| Deploy an app to a web host | /wbDeploy | wbDeploy/ |
| Inject premium gating | /wbLicense | wbLicense/ |
| Generate release announcement kit | /wbBroadcast | wbBroadcast/ |
| Bootstrap Free/Pro/Dev tier plumbing | /wbMonetize | wbMonetize/ |
| Commit code with Conventional Commits | /wbGit | wbGit/ |
| Append a quick log note to the session tracker | /wbLog | wbLog/ |
| Red-team scan: secrets, XSS, insecure deps | /wbSecure | wbSecure/ |
| Pull hardcoded strings to i18n keys | /wbTranslate | wbTranslate/ |
| Rewrite legacy/Vuetify into wbc-ui2 | /wbToWBC | wbToWBC/ |
Toggle session-wide logging of /wb* invocations | /wbTrack | wbTrack/ |
| Finalize a session and archive the tracker | /wbStopTrack | wbStopTrack/ |
How to navigate to a command's docs
Two patterns:
# By question (most common — daily use)
daily_use/README.md → scenario table → command name → commands/<cmd>/<cmd>_practical.md
# By concept (when you want to understand mechanics first)
concepts/README.md → overview file → command name → commands/<cmd>/<cmd>_expert.mdIf you're already in a command's folder and want to switch layers (e.g., you read practical and want examples), the files are siblings — no navigation needed.
Recommended reading order for first-time encounters
When you're about to run a command for the first time:
hub (wbX.md) → eli5 → practical → (run it once) → examples → (run it again)Skip expert unless you're modifying the command's runtime template.
The machine-readable catalog
wb_commands_reference.json is the same 33-command catalog in JSON form, suitable for tooling that needs to introspect the command surface programmatically.
What this folder is NOT
- Not a tutorial. For first-time onboarding, go to
../start_here/. - Not a daily playbook. For "what to run at 10am vs. 4pm," go to
../daily_use/. - Not the runtime templates. The source-of-truth
_template.mdfiles that define what each command actually does live inpackages/wb-flow/templates/commands/. This folder documents how to use them.