Threads

Use this skill to turn a broad request into controlled Codex-native subthreads with explicit lanes, file ownership, review gates, and verifiable closure.

Native Codex threads are short-lived parallel work lines inside the Codex workflow. They are not the same as OMX/tmux workers. If native subagent tools are not visible, discover them with tool search. If no native subagent capability is available, produce the thread prompt pack and execution plan instead of pretending threads were launched.

Quick Path

1. Classify the request: single_agent, plan_only, execute_direct, review_only, research_spec, or clarify_first.
2. If the user explicitly asked for threads, record thread_dispatch_gate and spawn required native lanes before implementation.
3. For GitHub queues, fetch remote state in the coordinator lane, then write queue_gate, queue_ledger, and issue_to_pr_map.
4. Write a lane map with file ownership, verification owner, stop conditions, context budget, and output firewall.
5. Route large command output to artifacts before dispatch; the parent reads only summaries, short tails, targeted greps, and evidence paths.
6. Dispatch only bounded native lanes with disjoint writable scopes or read-only roles.
7. Collect, wait, and close spawned agents; do not count the coordinator as a spawned thread.
8. Run fresh verification tied to the current head or artifact.
9. End with a compact final report and threads_run_log; write durable JSONL for queue, multi-lane, push, comment, or merge-capable runs.

Do Not Use For