メニュー
Primary entrypoint for Codex Orchestrator usage: route tasks to the right pipeline, mode, and supporting skills with minimal, auditable steps.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | codex-orchestrator |
| description | Primary entrypoint for Codex Orchestrator usage: route tasks to the right pipeline, mode, and supporting skills with minimal, auditable steps. |
Use this skill as the default entrypoint for work in CO or downstream repos using @kbediako/codex-orchestrator. It routes intent to the smallest correct command path and points to specialized skills only when needed.
runtimeMode=cli|appserverexecutionMode=mcp|cloudFor most task-scoped work:
codex-orchestrator flow --task <task-id>codex-orchestrator doctor --usage --window-days 30 --task <task-id>codex-orchestrator review --task <task-id>For explicit stage control:
codex-orchestrator start docs-review --task <task-id> --format jsoncodex-orchestrator start implementation-gate --task <task-id> --format jsoncodex-orchestrator status --run <run-id> --watch --interval 10docs-first.delegation-usage.collab-subagents-first.collab-deliberation.long-poll-wait.standalone-review, then elegance-review.release.collab-evals.0.135.0 and observed local 0.140.0 both keep js_repl and js_repl_tools_only removed; do not treat them as default-on, break-glass toggleable, or eligible for cloud feature lanes, and do not set cloud feature env vars or codex features enable/disable commands for either removed name.0.135.0 and observed local 0.140.0 both keep current guidance on explicit permission profiles and trust flows; do not recommend --full-auto as normal flow. Built-in config profile ids are :read-only, :workspace, and :danger-no-sandbox; no-sandbox profile selection is local-only advisory evidence.codex features list.memories stays scoped to explicit eval lanes.fork_context) is guidance-first: keep it false for bounded streams, and set true only when the child must inherit prior thread history.memory_tool; use memories in new CO guidance unless documenting legacy compatibility behavior.AGENTS.mddocs/AGENTS.mdREADME.mddocs/README.mddocs-firstdelegation-usagecollab-subagents-firstcollab-deliberationstandalone-reviewelegance-reviewlong-poll-waitreleaseagent-first-adoption-steeringManage non-trivial tasks via focused collab subagents to save context and improve throughput. Use when work spans multiple files/components, can be split into independent streams, needs separate validation/review, or risks context bloat. Favor direct execution for trivial one-shot tasks.
Ship a signed tag + GitHub Release + npm publish for @kbediako/codex-orchestrator with low-friction, agent-first steps (PR -> watch-merge -> tag -> watch publish -> downstream smoke).
Use when operating the Codex delegation MCP server and tools (delegate.spawn, delegate.question.*, delegate.cancel, github.merge confirmation flow), or when configuring delegation mode/tool_profile with delegation MCP enabled by default.
Use for required periodic cross-check reviews during implementation and before handoff using `codex review`.
Control and inspect Chrome via the Chrome DevTools MCP server (navigate, interact, screenshots, console, network, perf).
Run collab/multi-agent eval scenarios (symbolic RLM, large-context, pause/resume, multi-hour checkpoints) and capture manifest-backed evidence.