geo-pipeline

# geo-pipeline — Codex orchestrator for recomby-geo On Claude Code each stage is a bare slash command (`/01-intake` … `/07-reaudit`). Codex CLI has no bare custom commands, so this skill is the Codex entry point: it carries the orchestration rules and routes to the per-stage specification files, which are the **single source of truth** shared with the Claude Code side. Do not duplicate stage logic here — read the stage file and follow it. **Per-stage specs (read the one you're running):** `commands/01-intake.md`, `commands/02-audit.md`, `commands/03-gap.md`, `commands/04-content-brief.md`, `commands/05-production.md`, `commands/06-distribution.md`, `commands/07-reaudit.md` (relative to this plugin's root). Full directory convention + dependency graph: `orchestrator/run.md`. ## How to run a stage on Codex 1. Identify the client folder `clients/<slug>/` and the stage the user wants. 2. Read the matching `commands/0X-*.md` and execute its Procedure verbatim. 3. Validate every JSON artifact the stage writes against its schema before moving on (Codex has no built-in schema validation — run it explicitly): ```bash python3 - <<'PY' import json, jsonschema pairs = { "brand_context.json": "brand_context.schema.json", "visibility_baseline.json": "visibility_baseline.schema.json", "content_priorities.json": "content_priorities.schema.json", } # see schemas/ for the full set incl. attribution_diff + review_feedback # jsonschema.Draft202012Validat...