orchestrate
Orchestrate multi-step work with Claude Code CLI as a bounded worker while Codex stays lead developer. Use when Codex should split a task into scoped sub-tasks, delegate planning or implementation to Claude with `claude -p`, run parallel Claude sessions, isolate risky edits in worktrees, define custom Claude subagents, or move repeated enforcement into Claude hooks/settings.
Best use case
orchestrate is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Orchestrate multi-step work with Claude Code CLI as a bounded worker while Codex stays lead developer. Use when Codex should split a task into scoped sub-tasks, delegate planning or implementation to Claude with `claude -p`, run parallel Claude sessions, isolate risky edits in worktrees, define custom Claude subagents, or move repeated enforcement into Claude hooks/settings.
Teams using orchestrate should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/orchestrate/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How orchestrate Compares
| Feature / Agent | orchestrate | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Orchestrate multi-step work with Claude Code CLI as a bounded worker while Codex stays lead developer. Use when Codex should split a task into scoped sub-tasks, delegate planning or implementation to Claude with `claude -p`, run parallel Claude sessions, isolate risky edits in worktrees, define custom Claude subagents, or move repeated enforcement into Claude hooks/settings.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Orchestrate Keep architecture, acceptance, and integration local. Delegate bounded work only. ## Read the right reference - Read [references/orchestration.md](references/orchestration.md) for task decomposition, delegation rules, parallelism, context isolation, review loops, and evaluation. - Read [references/claude-cli.md](references/claude-cli.md) for the current `claude` CLI surface: `-p`, structured output, permission modes, worktrees, and custom agents. ## Lead versus worker - Lead (Codex): architecture, task graph, owned-file boundaries, acceptance criteria, integration, and final verification. - Worker (Claude): bounded research, boilerplate, repetitive refactors, first-pass implementation, docs, and mechanical edits. Do not hand off the part where a wrong decision would invalidate the rest of the work. ## When to use this skill - the task is larger than one coherent edit - multiple sub-tasks can run independently - a repetitive or high-volume slice can be delegated - you want Claude to work in an isolated worktree or with restricted tools - you need a repeatable orchestration pattern, not just a single prompt ## When not to use it - the next step is urgent and tightly coupled to your own reasoning - the change is trivial enough to do directly - the repo or task should not leave the current agent boundary - overlapping write scopes would make parallel work risky ## Default workflow 1. Define success, stop rules, and what stays local. 2. Break the task into atomic units with clear ownership. 3. Choose execution mode per unit: - read-only research or planning - bounded edit in current tree - isolated edit in a worktree 4. Build a short handoff with: - one concrete goal - files to read first - owned files and forbidden files - exact verification commands - return format 5. Run independent workers in parallel only when their write scopes do not overlap. 6. Review Claude’s output or diff before integrating. 7. Run local verification yourself. 8. If the pattern repeats, promote it into `.claude/agents`, hooks, or project settings. ## Core rules - Fresh Claude session by default for each delegated unit. - Use `--continue` only when continuity matters more than clean context. - Prefer structured output for plans, task maps, and review summaries. - Prefer tool and permission restrictions over prompt-only restrictions. - Use worktrees for risky or concurrent edit tasks. - Move deterministic enforcement into hooks, not repeated prose reminders. - Record what Claude owned, what you owned, and what was verified.
Related Skills
second-opinion
Run an external LLM code review with Codex CLI, Gemini CLI, or both. Use when the user asks for a second opinion, external review, Codex review, Gemini review, or wants a model-vs-model review of current changes, a branch diff, a specific commit, or a GitHub pull request.
seatbelt-sandboxer
Generates minimal macOS Seatbelt sandbox configurations. Use when sandboxing, isolating, or restricting macOS applications with allowlist-based profiles.
screenshot-analyzer
Find and analyze screenshots from ~/Downloads/Screenshots/ for UI/UX review. Use when asked to look at screenshots, review UI designs, inspect interface errors, analyze layout issues, or examine visual problems. Triggers on "check my latest screenshot", "review my UI", "analyze this screen capture".
save-session
Save AI agent session information for later resumption. Use when: (1) Finishing a work session and want to save progress (2) User says "save session", "remember this session", or "save your session ID" (3) Before ending a long coding/debugging session (4) When user wants to be able to resume this conversation later Supports Claude, Codex, Gemini, Copilot, Cursor, and other AI agents.
rust-profiling
Profile Rust code using samply to identify CPU bottlenecks. Use when performance is slow, before optimizing, or when the user asks to profile.
ratatui-tui
Build terminal UIs with ratatui following 2026 Rust best practices. Use when: (1) Creating new TUI apps, (2) Adding widgets/layouts, (3) Keyboard navigation/state management, (4) Image integration via ratatui-image, (5) Async event handling, (6) Release optimization. Covers v0.30.0+ API, Elm Architecture, StatefulWidget, color-eyre.
karpathy-guidelines
Behavioral checklist for disciplined LLM coding. Use when starting non-trivial tasks to enforce assumption surfacing, minimal changes, and verifiable goals. Derived from Andrej Karpathy's observations on LLM coding pitfalls.
instruments-profiling
Use when profiling native macOS or iOS apps with Instruments/xctrace. Covers correct binary selection, CLI arguments, exports, and common gotchas.
humanizer
Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases. 30c5c8d (Update humanizer plugin to upstream v2.2.0)
html-artifacts
Produce a single self-contained .html artifact (no build, no external assets) when the task is spatial, interactive, visual, multi-axis, or long-running. Triggers on "build me an HTML for X", "make a dashboard / status snapshot / comparison / decision tree / timeline / architecture map", "render this plan as a clickable site", or when content can't fit markdown structurally. Skips short replies, code-only outputs, simple plans.
handoff
Generate optimized handoff prompts for delegating work to another LLM agent. Use when handing work to GPT-5.x/Codex, Claude 4.x, Gemini 3.x, or Grok 4.x, either as a shared-workspace sub-task handoff or a fresh-context handoff for a new session or model. Triggers on requests like "create a handoff prompt", "delegate this task to another agent", "hand this off", or "prepare context for another agent".
go-performance
Measure and improve Go program performance on modern Go (1.24+). Use when profiling Go code, diagnosing CPU or memory bottlenecks, investigating latency or contention, writing or fixing benchmarks, comparing benchmark results, using pprof or trace data, applying PGO, or tuning hot-path Go code.