Maintain & Repair
mb-wiki
Last updated May 25, 2026
Unsupported in Codex
Explain wiki support status and keep planning read-only when the runtime cannot safely mutate wiki surfaces.
- Sense
- Decide
- Ship
- Reflect
Usage
Use mb-wiki 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-wiki
# Claude Code, when installed
/mb-wiki When to use it
Best for
A boundary route when the operator asks about wiki work, docs surfaces, or unsupported Codex workflow coverage.
Use when
- The operator asks for wiki support.
- A desired surface is inventoried but unsupported in Codex.
- The safest action is planning structure without mutation.
Route workflow
- Read the runtime workflow inventory.
- Explain that wiki mutation is not supported in Codex today.
- Offer a read-only page structure or plan.
- Route execution to a supported surface only after approval.
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 workflow list --runtime codex --json Command contract
Reads
- wiki support status
- docs needs
- repo context
Writes
- none; this is an unsupported Codex execution route today
Approval gates
- routing to Claude Code or another supported surface
- any external wiki mutation
- public documentation changes
Expected output
Return
- Support boundary.
- Read-only plan.
- Recommended supported route or runtime.
Do not
- Do not mutate wiki surfaces from Codex.
- Do not pretend unsupported routes are available.
- Do not leave the operator without a planning path.
Example response
Wiki mutation is not available in this runtime. I can plan the page structure and wait for approval before any public docs change.