Docs navigation mb-organic

Create & Ship

mb-organic

Last updated May 25, 2026

Read-only planning in Codex

Draft posts, newsletters, and queues from strategy, proof, research, and decisions.

mb-organic spans Decide, Ship
  1. Sense
  2. Decide
  3. Ship
  4. Reflect

Usage

Use mb-organic 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-organic

# Claude Code, when installed
/mb-organic

When to use it

Best for

A planning-only Codex route for organic posts, newsletters, content queues, and narrative angles grounded in owned context.

Use when

  • The operator asks for content ideas or drafts.
  • Voice, proof, offer, or strategy must shape the copy.
  • A content queue needs review before scheduling or publishing.

Route workflow

  1. Read current voice, offer, proof, research, and decisions.
  2. Choose the content job and channel.
  3. Draft or plan pieces with source context visible.
  4. Ask before writing durable queues, scheduling, posting, or contacting customers.

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

Command contract

Reads

  • voice
  • content strategy
  • proof
  • research
  • recent decisions

Writes

  • none in Codex by default; content plans and draft copy only

Approval gates

  • writing durable content queues
  • publishing
  • scheduled distribution
  • customer contact

Expected output

Return

  • Content angle or queue.
  • Draft copy grounded in proof.
  • Review notes and publish gate.

Do not

  • Do not schedule or publish from Codex by default.
  • Do not drift from the recorded voice.
  • Do not use generic content advice when repo proof exists.

Example response

agent
Draft three posts from the current offer decision, each grounded in proof and queued for operator review before posting.