Start & Status
mb-status
Last updated May 25, 2026
Supported in Codex
Show the current operating state before choosing a route or making a claim.
- Sense
- Decide
- Ship
- Reflect
Usage
Use mb-status as an agent route. The route should read Main Branch facts before advice, then stay inside the approval gates for the work it recommends.
mb-status
# Claude Code, when installed
/mb-statusWhen to use it
Best for
A read-only status check when the operator wants to know what is ready, stale, drifting, or newly changed.
Use when
- The operator asks for status.
- A route needs current facts before advice.
- You need to compare recent work, MoneyPath, provider posture, or ranked actions.
Route workflow
- Run the status fact command.
- Name readiness, drift, recent work, and since-last-check changes.
- Call out MoneyPath, content strategy, provider signals, and ranked actions when present.
- Recommend the next narrow route without writing files.
Safe fact commands
Run only the read-only facts needed for the route before recommending next work. Approval-gated commands belong in the plan, not the first move.
mb status --json --peekCommand contract
Reads
- setup readiness
- runtime drift
- recent work
- MoneyPath
- open decisions and checkpoints
Writes
- none
Approval gates
- none for read-only inspection
Expected output
Return
- Current readiness.
- Important drift or blockers.
- Ranked next actions grounded in status facts.
Do not
- Do not invent missing status signals.
- Do not turn status into a repair apply.
- Do not claim a provider is connected without evidence.
Example response
Status says the repo is initialized, provider posture needs review, and the highest-leverage next action is to close the open site-readiness push.