Decide
mb-think
Last updated May 25, 2026
Supported in Codex
Turn messy context into a durable decision, research note, or operating judgment.
- Sense
- Decide
- Ship
- Reflect
Usage
Use mb-think 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-think
# Claude Code, when installed
/mb-think When to use it
Best for
A decision route when the operator needs judgment, research depth, or durable business context before execution.
Use when
- The next move is unclear.
- A bet, offer, content angle, or page decision needs evidence.
- The operator wants the agent to think before writing or shipping.
Route workflow
- Choose the smallest honest research depth.
- Read only the business files needed for the decision.
- Separate facts, assumptions, options, and recommendation.
- Ask before codifying memory or checkpointing.
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 --peek
mb start --json
mb doctor repair --plan
mb connect doctor --json
mb checkpoint --plan --json Command contract
Reads
- core files
- research
- decisions
- offers
- audience notes
- proof
Writes
- research notes, decision records, or checkpoint plans only after approval
Approval gates
- durable memory edits
- checkpoint saves
- external research purchases or account actions
Expected output
Return
- Decision frame.
- Evidence and tradeoffs.
- Recommendation plus approval boundary for any durable save.
Do not
- Do not over-research routine questions.
- Do not write decision records without approval.
- Do not blur facts and assumptions.
Example response
The best wager is to narrow the offer around founder-led ads setup, then record the positioning decision before drafting copy.