/wbTrack — Start session tracking
Overview
/wbTrack initializes a session tracking file that records every /wb* command invocation, creating a narrative of the work session. It appends timestamped entries for each command run, capturing the command, target, and outcome. The tracking file serves as the session's audit trail, enabling /wbStandup to produce accurate summaries and /wbNext to make informed recommendations based on actual workflow history.
When to Use
Run this when: You are starting a work session and want to track all actions for later review and handoff.
📚 Layer Files
| Layer | File | What you'll learn |
|---|---|---|
| ELI5 | wbTrack_eli5.md | What this command does in plain English |
| Practical | wbTrack_practical.md | A step-by-step walkthrough on a real project |
| Expert | wbTrack_expert.md | Architecture, edge cases, and when NOT to use |
| Examples | README.md (merged) | Annotated transcripts from actual sessions |
| Simulation | wbTrack_exhaustive_simulation.md | Exhaustive flag-matrix and failure-mode coverage |
| Live Demo | wbTrack_live_demo.md | Real-time execution on an actual codebase |
What This Command Does NOT Do
- ❌ Does not summarize the session — use
/wbStandupfor that. - ❌ Does not stop tracking — use
/wbStopTrackfor that. - ❌ Does not plan work — use
/wbPlanfor that.
What's Next?
After reading this hub, either:
- Pick a layer file above for deep reading
- Run
/wbNextto see what commands naturally follow/wbTrackin a workflow
How It Works
Records timestamp, branch, task, project context, and billing metadata.
Flags & Shortcuts
Both forms are equivalent — pass either:
| Long form | Shortcut |
|---|---|
--finalize | -f |
--scope | -s |
--snap | — |
--next | — |
-h / --help / --h (any command) prints this help block instead of executing.
← Home · Commands · Install | wb-flow on npm · flow.wbc-ui.com · wi-bg.com
