$npx -y skills add 100yenadmin/fable-token-saving-skills-orchestrator --skill codex-dispatchUse when routing well-specified implementation work from Fable to Codex or another side worker.
| 1 | # Codex Dispatch |
| 2 | |
| 3 | Premium tokens buy judgment. Codex or side-worker capacity buys implementation |
| 4 | volume when the task is well specified. |
| 5 | |
| 6 | ## Dispatch When |
| 7 | |
| 8 | - the task is self-contained |
| 9 | - the spec carries enough context |
| 10 | - acceptance criteria are explicit |
| 11 | - the work can happen on a side branch or bounded file set |
| 12 | - Fable can review the result instead of typing it |
| 13 | |
| 14 | ## Keep With Fable Or A Higher Local Lane When |
| 15 | |
| 16 | - the task is architecture, product strategy, or final judgment |
| 17 | - the implementation depends on local-only tools the side worker lacks |
| 18 | - the acceptance criteria are unclear |
| 19 | - the task requires private credentials or live user action |
| 20 | |
| 21 | ## Dispatch Packet |
| 22 | |
| 23 | Include: |
| 24 | |
| 25 | - objective |
| 26 | - repo/path/branch |
| 27 | - files or areas involved |
| 28 | - constraints and non-goals |
| 29 | - pseudocode for hard parts |
| 30 | - exact validation command or CI gate |
| 31 | - proof boundary |
| 32 | - expected final report shape |
| 33 | |
| 34 | ## Mechanics |
| 35 | |
| 36 | Some lanes are reachable through a CLI rather than a workflow model parameter. |
| 37 | When a background shell launches a side worker, close stdin explicitly if the |
| 38 | tool expects EOF. For Codex CLI, use: |
| 39 | |
| 40 | ```bash |
| 41 | codex exec --cd <worktree> "<prompt>" < /dev/null |
| 42 | ``` |
| 43 | |
| 44 | Without the redirected stdin, some background shells can leave the worker |
| 45 | waiting at startup instead of doing work. |
| 46 | |
| 47 | ## Skill Availability |
| 48 | |
| 49 | Side workers do not automatically see every local Claude skill. Port skills on |
| 50 | demand when a dispatch needs them; do not mirror an entire skill library by |
| 51 | default. |
| 52 | |
| 53 | Example: |
| 54 | |
| 55 | ```bash |
| 56 | ln -sfn "$HOME/.claude/skills/<skill>" "$HOME/.codex/skills/<skill>" |
| 57 | ``` |
| 58 | |
| 59 | Name the required skill in the dispatch packet and keep the accepted output |
| 60 | bounded. If the side worker lacks a required skill and the work is not |
| 61 | self-contained, keep the task with Fable or a local lane. |
| 62 | |
| 63 | ## Review Rule |
| 64 | |
| 65 | If the diff or report is large, ask a fast worker for a bounded digest first. |
| 66 | Fable reads the digest and flagged hunks, not the whole raw output. |
| 67 | |
| 68 | ## Attribution And Adjacent Tools |
| 69 | |
| 70 | This dispatch pattern is inspired in part by |
| 71 | [blader/arbitrage](https://github.com/blader/arbitrage), which focuses on |
| 72 | premium-model judgment plus Codex implementation. Claude Code users who want a |
| 73 | slash-command bridge to Codex review and delegation workflows can also look at |
| 74 | [openai/codex-plugin-cc](https://github.com/openai/codex-plugin-cc). |
| 75 | |
| 76 | FTSO's own guidance remains tool-agnostic: write the spec first, dispatch only |
| 77 | bounded work, review the output before accepting it, keep turns dense while |
| 78 | lanes run, and name the proof boundary. |