Main Branch Owner Loop

---
name: main-branch-owner-loop
description: >-
  Use when the operator asks Codex to run Main Branch daily owner-loop work from a business repo: start/status/setup/update/doctor, think/codify, end/checkpoint/save, validate, or workflow discovery. Starts from deterministic mb facts and asks before durable writes, provider mutations, publishing, spend, customer contact, or checkpoints.
---

# Main Branch owner loop for Codex

Run Main Branch owner-loop work from a business repo. This is a Codex-native
skill generated by `mb`; `AGENTS.md` remains the repo-level bootstrap.

## Start Here

Before advice, run read-only facts that fit the request:

- `mb --version`
- `mb status --json --peek`
- `mb start --json`
- `mb doctor repair --plan --json`
- `mb update --check --json`
- `mb validate --json`
- `mb checkpoint --plan --json`
- `mb workflow list --runtime codex --json`

Run `command -v mb` and `mb --version` as a standalone runtime preflight before
substantive `mb` commands. This guidance was generated by Main Branch
`0.3.33`. If the runtime reports an older or different version, stop and
tell the operator to put the current Main Branch install earlier on the
runtime/login-shell PATH before continuing.

After `mb status --json --peek` or `mb start --json`, stop if `runtime.codex_cli.status` is `runtime_mismatch` or any `drift.items[].id` equals `codex_runtime_mb_mismatch`. Treat that as a runtime `mb` mismatch: tell the operator to fix the runtime/login-shell PATH and rerun read-only checks before owner-loop advice, repair planning, or writes.

Use `mb status --json --peek` as the first daily read. Use `mb start --json`
when runtime handoff or adapter readiness matters. Use
`mb workflow list --runtime codex --json` when the operator asks what Codex can
do.

## Supported Owner Loop

- start/status/setup/update/doctor: inspect facts and plans, then ask before
  applying repairs, migrations, setup writes, or updates.
- think/codify: follow the `mb-think` shared workflow route in `AGENTS.md`.
- end/checkpoint/save: run `mb checkpoint --plan --json`, propose a
  business-readable checkpoint, and ask before saving it.
- validate: run `mb validate --json` and explain repo health in business
  language before technical details.
- workflow discovery: read `references/workflow-inventory.md` or run
  `mb workflow list --runtime codex --json`.

## Approval Gates

Ask before durable writes, checkpoints, updates, repairs, migrations, provider
mutation, publishing, spend, customer contact, destructive operations, raw
private-source reads, or public issue/proposal submission.

Do not claim Claude Code slash-skill parity in Codex. Do not claim ads, site,
organic, provider mutation, wiki, or skill-authoring parity unless the
inventory marks that surface `supported`.