القائمة
Use when a task requires a spec-driven workflow: draft/refresh PRD + TECH_SPEC + ACTION_PLAN + tasks, link TECH_SPEC in tasks/index.json, and run docs-review before implementation.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Primary entrypoint for Codex Orchestrator usage: route tasks to the right pipeline, mode, and supporting skills with minimal, auditable steps.
Manage 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).
استنادا إلى تصنيف SOC المهني
| name | docs-first |
| description | Use when a task requires a spec-driven workflow: draft/refresh PRD + TECH_SPEC + ACTION_PLAN + tasks, link TECH_SPEC in tasks/index.json, and run docs-review before implementation. |
Use this skill when a task needs a spec-driven workflow. The objective is to create or refresh PRD + TECH_SPEC + ACTION_PLAN + the task checklist before editing code or docs, capture a brief translation of the user’s request in the PRD for context retention, and keep task mirrors and review evidence in sync as understanding evolves.
For shipped CO usage, default to this command path unless task constraints say otherwise:
codex-orchestrator flow --task <task-id>codex-orchestrator doctor --usage --window-days 30 --task <task-id>codex-orchestrator rlm --multi-agent auto "<goal>".agent/task/templates/prd-template.md)..agent/task/templates/tech-spec-template.md; stored under tasks/specs/<id>-<slug>.md)..agent/task/templates/action-plan-template.md).docs/micro-task-path.md instead of long-form rewrites (still requires task/spec evidence).tasks/index.json (including last_review).tasks/tasks-*.md) and mirror to .agent/task/.docs/TASKS.md with the snapshot entry.npx codex-orchestrator start docs-review --format json --no-interactive --task <task-id>CODEX_CLOUD_BRANCH=main (or another pushed branch).docs/AGENTS.mddocs/guides/instructions.mddelegation-usage: for task-scoped delegated research/review streams after docs scaffolding.standalone-review: for pre-implementation approval and implementation checkpoints.elegance-review: for post-implementation minimality pass before handoff.agent-first-adoption-steering: for non-blocking advanced-feature steering and option framing.