/wbNext — Live Demo ()
This is what /wbNext actually does on wb-labs as the workspace stands today (2026-05-05). The matrix below mirrors the exhaustive simulation, but every cell is filled from the live state of the repo.
1. Live target
| Field | Live value |
|---|---|
| Active package | core2/packages/wb-core |
| Active plan | reports/20260504/plans/plan_wb-core_20260504.md |
| Plan state | Row 1 ✅✅, Row 2 ✅✅, Row 3 ⬜⬜ (deps satisfied) |
| Deterministic answer | Row 3 (the only eligible task) |
This is the simplest possible DAG state for /wbNext: two completed rows, one ready row, zero ambiguity.
2. What each argument resolves to today
| Argument | Live resolution |
|---|---|
/wbNext packages/wb-core | Row 3. Only eligible task. |
/wbNext (from core2 root) | Reads monorepo-level plan (if exists). If none, suggests /wbPlan. |
/wbNext apps/* | Per-app next: demo=Task 3, md=complete, wbc-ui=Task 1 (auth fix). |
/wbNext packages/wb-core -s="complexity" | Still Row 3 — only one candidate, sort is a no-op. |
3. Per-flag behavior, applied live
| Flag | If invoked now |
|---|---|
/wbNext packages/wb-core | [NEXT] Task 3: WBC.js decomposition. Run /wbWork --id="3". |
/wbNext packages/wb-core -e | Adds DAG trace: "Row 1 complete, Row 2 complete, Row 3 eligible (deps 1,2 satisfied)." |
/wbNext packages/wb-core -a | Auto-executes /wbWork --id="3". No confirmation. WBC.js decomposition begins. |
/wbNext packages/wb-core -a -e | DAG trace + auto-execute. Full autonomous mode. |
/wbNext packages/wb-core -s="priority" | Same answer (Row 3 is the only candidate). Warns if no Priority column. |
4. Pipelines
/wbNext Live Execution Simulator
Standard query
/wbNext packages/wb-core> /wbNext packages/wb-core[SYSTEM] Querying DAG...
[READ] plan_wb-core_20260504.md (3 rows)
[NEXT] Task 3: WBC.js decomposition
Status: ⬜ Pending | Deps: 1, 2 (both ✅)
[RECOMMENDATION] Run `/wbWork --id="3"` to execute.
💠 Pipeline Standard query
💠 Pipeline Autonomous execution with trace
💠 Pipeline Multi-app next with priority sort
5. What would refuse today
| Trigger | Live response |
|---|---|
/wbNext packages/wb-core after all rows are ✅ Done + ✅ Valid | ✅ Plan complete. No remaining tasks. Run /wbGit to commit. |
/wbNext packages/wb-core --act on a plan where all tasks are blocked | ❌ All pending tasks are DAG-blocked. Cannot auto-execute. Fix dependencies first. |
/wbNext packages/nonexistent | ❌ No plan found in packages/nonexistent. |
/wbNext -s="urgency" when plan has no Urgency column | ⚠️ Plan lacks "urgency" metadata. Falling back to chronological order. |
The pattern: /wbNext gives one answer — the right one — or explains why it can't. No menus, no alternatives, no "you might also consider." That narrowness is what makes it safe for --act chains.