orchestration-strategy

Selects cost-efficient orchestration strategies for multi-task workloads using decision criteria and worktree isolation.

1|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/cjthompson/claude-code-config --skill orchestration-strategy-cjthompson
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orchestration-strategy
Source: https://github.com/cjthompson/claude-code-config/tree/main/plugins/orchestration-strategy/skills/orchestration-strategy
Command: npx skills add https://github.com/cjthompson/claude-code-config --skill orchestration-strategy-cjthompson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When facing multiple implementation tasks, it is hard to decide whether to work solo, spawn parallel agents, run sequential subagents, or use Agent Teams — and choosing wrong wastes tokens or causes merge conflicts. This Skill provides a structured decision process that picks the cheapest strategy satisfying the task's coordination needs. ## Core Features & Use Cases - Four-strategy decision framework: Evaluates solo, parallel agents, sequential subagents, and Agent Teams against task count, independence, file overlap, merge complexity, and communication needs. - Worktree-based parallelism: Uses detached-HEAD git worktrees plus a cherry-pick integration protocol so tasks with trivial file overlap can still run in parallel safely. - Explicit handoff contracts: Generates constraint checklists for downstream execution skills covering isolation strategy, integration ordering, autonomy level, and model selection. - Use Case: Given an implementation plan with 8 tasks, some sharing files, the Skill reads the plan and source files, determines that worktree-isolated parallel agents are viable, and hands off explicit squash-and-cherry-pick instructions to the dispatching skill. ## Quick Start Ask the AI to evaluate the implementation plan and choose the most cost-efficient orchestration strategy for executing these tasks.

Frequently Asked Questions about orchestration-strategy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I decide between parallel agents and sequential subagents?

Choose parallel agents when tasks are independent with no file overlap, or when overlap is trivial and worktree isolation is available. Choose sequential subagents when tasks have dependency chains, semantic file overlap, or require review gates between steps.

When should I use Agent Teams instead of parallel agents?

Use Agent Teams only when workers need inter-agent communication such as debating or negotiating mid-work. Teams cost 3-7x more than parallel agents, so for well-defined independent tasks parallel agents are cheaper and sufficient.

Can tasks that modify the same file still run in parallel?

Yes, if the changes are additive and trivial, such as new functions or module declarations, using git worktree isolation with cherry-pick integration. If tasks modify the same struct, function, or code block, sequential execution is safer.

How does worktree isolation with cherry-pick integration work?

Each agent works in a detached-HEAD worktree under .claude/worktrees/, squashes its work into a single commit, and reports the hash. The leader then cherry-picks commits in dependency order, running builds and tests after each integration.

What happens if Agent Teams are not enabled in my environment?

The Skill detects whether the TeamCreate tool is available. If teams are unavailable, it falls back to parallel agents or sequential subagents and explains the specific trade-off of the fallback strategy to the user.

Why re-evaluate the orchestration strategy after each task batch?

Task characteristics change as work completes — a finished foundation task may unlock parallelism that was not viable before. Re-running the decision analysis after each dependency tier ensures the strategy stays cost-efficient.