This guide answers the practical question: after installation, how should a developer actually use BBMstack day to day?
After installing BBMstack and adding .bbmstack.json to the project:
bbmstack source sync
bbmstack activate
bbmstack checkThen restart Claude Code or Codex if the new skills do not appear immediately.
Use these as your default entrypoints:
/planwhen the work is still vague or the architecture is not locked/debugwhen something is broken and you need root cause analysis/qawhen you want browser-driven testing and fixes/reviewwhen you want a paranoid pre-merge check/shipwhen work is complete and you want to verify and prepare it for release/verifywhen you need explicit completion checks before claiming something is done
For most feature work:
- Start with
/plan - Implement the work
- Run
/review - Run
/qaif the change affects user-facing behavior - Run
/shipor/verify
For debugging:
- Start with
/debug - Fix the issue
- Run
/review - Run
/verify
For browser-heavy work:
- Use
/setup-browserif auth cookies are needed - Use
/browsefor manual browser investigation - Use
/qafor systematic testing
/plan → implement → /review → /qa → /ship
/debug → implement fix → /review → /verify
/plan → implement → /review → /verify
bbmstack source sync → bbmstack activate → /plan or /review
If your project uses only public sources:
cp ~/Dev/BBMstack/examples/bbmstack.json .bbmstack.json
bbmstack source sync
bbmstack activateIf your project also uses a private source:
cp ~/Dev/BBMstack/examples/bbmstack.private.json .bbmstack.json
bbmstack source sync
bbmstack activateIf the private source cannot be cloned, BBMstack will continue with public sources and report the private source as missing.
Resolve source state:
bbmstack source listSync enabled sources:
bbmstack source syncActivate configured packs:
bbmstack activateCheck installation and project status:
bbmstack checkFor new developers, the minimum useful onboarding is:
- Install BBMstack
- Add the project
.bbmstack.json - Run
bbmstack source sync - Run
bbmstack activate - Start with
/plan,/debug,/qa,/review, or/ship
This avoids spending the first hour teaching the agent your workflow from scratch.