cc-sync-runnerlisted

# CC Sync Runner Produce a corrected CC-to-Codex plan and the next public-safe Codex skill/batch drafts. Implementation is a separate explicit mode. Do not copy `.claude/` files into Codex. Treat `.claude/` as read-only. The default output is not a critique. It is a replacement planning package that answers: - What Claude Code currently has. - What Codex already covers. - What Codex lacks. - Which gaps are public-safe, private-only, redacted, or manual-review. - What verification scripts/tests must exist before any implementation is considered done. - Which new Codex skills or skill skeletons must be created. ## Market Pattern Use the standard builder loop: 1. Durable rules in `AGENTS.md`. 2. Repeatable workflow in this skill. 3. Long-horizon state in `docs/CODEX_BATCHES.md`. 4. Machine checks in `scripts/codex_check.py`. 5. Stop hooks and reports to prevent early finish. 6. Optional `codex exec` automation later, after local runs are stable. This is not "one giant prompt". It is a bounded planning-production loop: ```text raw sync plan -> subagent audits -> capability gap ledger -> replacement sync plan -> new skill specs/skeletons -> proposed batches/checks -> final plan audit -> stop ``` ## Modes ### Planning Mode Default mode for requests like "sync CC to Codex", "run CC sync", "review CC_SYNC_PLAN", "rewrite the plan", "what does Codex lack", "create the missing Codex skill", or "make a plan". Planning Mode must not: - claim a b