Codex Runtime Routing Instructions
# Codex Runtime Routing Instructions
Use this file when you want Codex to choose the right Co-Evolution entrypoint before it starts work.
## Default Rule
Pick the lowest-ceremony path that still protects correctness. **Start with `co-evolve-bouncer.sh` unless the task specifically needs code execution.**
## Route By Task Shape
| Task shape | Use | Why |
|------------|-----|-----|
| Any question, idea, or strategy that benefits from cross-AI refinement | `bash co-evolve-bouncer.sh --vanilla "question"` | General-purpose compose + bounce |
| Markdown plan, spec, RFC, or document needs refinement | `bash co-evolve-bouncer.sh --vanilla --bounce-only <file>` | Bounces existing doc without compose |
| High-stakes question or argument that needs deep stress-testing | `bash co-evolve-bouncer.sh --vanilla --chain "input"` | Staged: critique → defend → tighten |
| 1-2 files, low risk, obvious implementation | direct execution | Fastest path when planning overhead is not useful |
| 2+ files, medium risk, ambiguous approach, needs code execution | `bash dev-review/codex/dev-review.sh <task>` | Adds compose, bounce, AND code execution |
| Existing approved plan should be executed as-is | `bash dev-review/codex/dev-review.sh --skip-plan --plan <file>` | Reuses the approved plan |
| User wants a reviewed plan before any code changes | `bash co-evolve-bouncer.sh --vanilla "task"` or `dev-review.sh --plan-only` | Plan artifact only |
| User wants a final review against the plan and diff | `bash dev-review/codex/dev-review.sh --verify <task>` | Runs verifier after execution |
| Orchestrated / background build — plan and review in-session, Codex executes detached | `CO_EVOLVE_TOKEN_CAPTURE=1 bash dev-review/codex/dev-review.sh --preset codex-build --skip-plan --plan <file> --branch auto -- "<task>"` (kicked in the background; see `skills/codex-build/`) | Model-ladder ladder: best Claude (Opus) plans/reviews, Codex executes; session is not babysat |
| Orchestrated build on Claude — Codex plans/reviews, Claude executes (synchronous) | `bash dev-review/codex/dev-review.sh --preset claude-build --skip-plan --plan <file> --worktree auto -- "<task>"` (see `dev-review/codex/claude-build.md`) | Mirror ladder: Codex plans/reviews, Claude executes; hard-requires claude auth |
| Ad-hoc interactive delegation to Codex mid-session | OpenAI plugin `/codex:rescue --background` (see `skills/codex-build/` Transport B) | Quick delegation; review with the same verdict schema by hand, not via CI |
## Distinguish Coding From Everything Else
Use `co-evolve-bouncer.sh` when the deliverable is a refined answer, document, or plan:
- questions and strategy
- plan refinement
- prompt tuning
- design notes
- architecture docs
- legal arguments
- draft emails
Use `dev-review.sh` when the deliverable is code plus an execution trail:
- feature work
- bug fixes
- refactors with repo edits
- tasks where optional verification is worth the extra pass
Use direct execution when the task is too small to justify the pipeline:
- typo fixes
- single-line config edits
- obvious narrow updates in 1-2 files
## co-evolve-bouncer.sh Key Flagswhen to use it
Community prompt sourced from the open-source GitHub repo alanshurafa/co-evolution (MIT). A "Codex Runtime Routing Instructions" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
productivitycommunitydeveloper
source
alanshurafa/co-evolution · MIT
more in Productivity
Productivity✓ tested
Summarize a doc into decisions & actions
chief of staff who extracts what to DO, not just what was said
Productivity✓ tested
Draft a reply to a hard email
calm, direct communicator who de-escalates without caving
Productivity✓ tested
Turn a brain-dump into a weekly plan
planning coach who protects your focus, not just your calendar