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.
What this skill does
# 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 in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.