run-batch-codex-research

Fan out one prompt template across N inputs through an LLM CLI (codex, claude, gemini, ollama, …), running with bounded concurrency, writing one answer file per input, skipping inputs whose answer already exists, and retrying only the failed ones. The unit of work is (template, input) → answers/<slug>.md.

This skill stays small on purpose. It is the generic, CLI-agnostic batch fanout pattern. If the run is codex-only and needs worktrees, manifests, monitor events, or one of the other codex modes (exec / single / review / rescue), reach for orchestrate-codex instead.

When to reach for this skill

Use it if any of these phrases describe the task — italicized so the agent matches them at trigger time:

• "run codex over each URL in urls.txt", "for each input in this list, run the prompt", "fan out the template across N IDs"
• "batch this prompt over a CSV of items", "one answer file per row"
• "parallel research across many topics", "do this for every entry and save the output"
• "resume the batch — retry just the ones that failed", "idempotent, skip already-done inputs"
• "swap codex for claude / gemini / ollama and re-run the same batch"
• "limit to N concurrent CLI processes", "don't melt my machine, cap at 8 jobs"

Do NOT use this skill when: