agent-orchestration

Selects models, roles, and effort levels for delegating work across AI agents.

1|Updated Jul 3, 2026
One-click install
npx skills add https://github.com/nejcm/agents --skill agent-orchestration-nejcm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-orchestration
Source: https://github.com/nejcm/agents/tree/main/skills/agent-orchestration
Command: npx skills add https://github.com/nejcm/agents --skill agent-orchestration-nejcm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deciding which AI model should handle a task, how much reasoning effort to apply, and how to split work across multiple agents is error-prone and inconsistent. This Skill provides a structured decision framework for delegation so work is routed to the right model with the right role and effort every time. ## Core Features & Use Cases - Model and Role Selection: Ranks models by intelligence, taste, and cost, and maps them to Planner, Builder, Reviewer/Judge, and cheap-worker roles with explicit fallback orders. - Delegation Patterns: Supports specialist, fan-out, staged plan/build/review/fix, and second-opinion patterns with rules for parallelization and retry limits. - Delegation Packets: Defines a structured packet format covering objectives, success criteria, constraints, style rules, and verification steps so delegates receive complete context. - Use Case: When implementing a feature, use this Skill to route planning to a high-intelligence model, building to a cost-effective Builder, and review to an independent cross-family Reviewer, then coordinate fixes through staged phases. ## Quick Start Ask the agent to decide whether this task should be delegated and to which model, role, and effort level using the agent-orchestration skill.

Frequently Asked Questions about agent-orchestration

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

FAQPage Schema
How do I decide which AI model to delegate a coding task to?▼

Rank candidate models by intelligence, taste, and cost, then match the task to a capability role. Bulk mechanical work goes to cost-effective Builders, while user-facing or architectural work needs models with high taste and intelligence scores.

When should I use a staged plan-build-review workflow with AI agents?▼

Use the staged pattern only when independent review materially reduces risk. The orchestrator coordinates phases without editing code, while separate Planner, Builder, and Reviewer agents handle planning, implementation, and adjudication of findings.

What is a delegation packet and what should it contain?▼

A delegation packet is the context sent to a delegate agent. It includes the objective, success criteria, role and effort, target revisions, constraints, style rules quoted verbatim, allowed verification commands, and the required return format.

Can a Builder agent review its own code changes?▼

No. A Builder must never review its own diff or adjudicate objections to its own review. Independent review requires a different model, preferably from a different model family, with same-family fallbacks disclosed.

How many parallel agents should I run for one task?▼

Use no more than three distinct automatic delegates and at most one per role unless scopes differ. Parallelize only independent work, keep dependent phases sequential, and resume existing agents for fixes instead of spawning new ones.