Reflect

mb-end

Last updated May 25, 2026

Supported in Codex

Crystallize what changed, save lessons, and checkpoint approved progress.

mb-end spans Reflect

Sense
Decide
Ship
Reflect

Usage

Use mb-end as an agent route. The route should read Main Branch facts before advice, then stay inside the approval gates for the work it recommends.

bash

mb-end

# Claude Code, when installed
/mb-end

When to use it

Best for

A closeout route when the operator wants a session summary, lesson capture, or checkpoint plan before stopping work.

Use when

A work session is ending.
The operator needs to know what changed and what remains open.
A checkpoint, commit, or durable memory update may be appropriate.

Route workflow

Scan current status and changed work.
Summarize what changed, what was learned, and what is unresolved.
Produce a checkpoint plan or owner-facing save state.
Ask before saving checkpoints, committing, or editing durable memory.

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.

bash

mb status --json --peek
mb start --json
mb doctor repair --plan
mb checkpoint --plan --json
mb validate --json

Command contract

Reads

session work
changed files
bets
pushes
decisions
outcomes

Writes

checkpoint summaries, lessons, or updated records after approval

Approval gates

commits
checkpoints
durable memory edits

Expected output

Return

Session summary.
Final thought or crystallized lesson.
Checkpoint plan and next-session handoff.

Do not

Do not save checkpoint files without approval.
Do not omit failed checks or unresolved risks.
Do not bury next actions in a long transcript.

Example response

agent

Record that the command-menu IA changed, the next work is individual command pages, and the checks passed.