Agent Orchestration

by parcadeid07ff4b06b62No license3.9K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 8 months ago

Agent Orchestration Rules

Instructions onlyAI & Agents

AI-generated overview

Guides an agent to delegate implementation work to subagents to preserve main-context tokens.

What it does: This skill provides rules for deciding when to spawn implementation subagents instead of doing work in the main conversation. It contrasts context-burning direct work with delegating multi-file implementation, plan phases, and feature work with tests to agents, and includes a sample delegation prompt and trigger words. It produces guidance, not files or code.
When to use it: Use it when a user asks to implement, build, or create a feature, or to follow a plan phase, and you want to keep the main context small. It is also relevant when deciding whether a task is too small to justify an agent.
Requirements: No tools, packages, or credentials; it is instructions only and ships no scripts.

Agent Orchestration Rules

When the user asks to implement something, use implementation agents to preserve main context.

The Pattern

Wrong - burns context:

Main: Read files → Understand → Make edits → Report      (2000+ tokens consumed in main context)

Main: Read files → Understand → Make edits → Report      (2000+ tokens consumed in main context)

Right - preserves context:

Main: Spawn agent("implement X per plan")      ↓Agent: Reads files → Understands → Edits → Tests      ↓Main: Gets summary (~200 tokens)

Main: Spawn agent("implement X per plan")      ↓Agent: Reads files → Understands → Edits → Tests      ↓Main: Gets summary (~200 tokens)

When to Use Agents

Task Type	Use Agent?	Reason
Multi-file implementation	Yes	Agent handles complexity internally
Following a plan phase	Yes	Agent reads plan, implements
New feature with tests	Yes	Agent can run tests
Single-line fix	No	Faster to do directly
Quick config change	No	Overhead not worth it

Key Insight

Agents read their own context. Don't read files in main chat just to understand what to pass to an agent - give them the task and they figure it out.

Example Prompt

Implement Phase 4: Outcome Marking Hook from the Artifact Index plan.
**Plan location:** thoughts/shared/plans/2025-12-24-artifact-index.md (search for "Phase 4")
**What to create:**1. TypeScript hook2. Shell wrapper3. Python script4. Register in settings.json
When done, provide a summary of files created and any issues.

Implement Phase 4: Outcome Marking Hook from the Artifact Index plan.
**Plan location:** thoughts/shared/plans/2025-12-24-artifact-index.md (search for "Phase 4")
**What to create:**1. TypeScript hook2. Shell wrapper3. Python script4. Register in settings.json
When done, provide a summary of files created and any issues.

Trigger Words

When user says these, consider using an agent:

"implement", "build", "create feature"
"follow the plan", "do phase X"
"use implementation agents"

Source and attribution

Source:parcadei/continuous-claude-v3in.claude/skills/agent-orchestrationat commitd07ff4b

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

Agent Orchestration

Agent Orchestration Rules

The Pattern

When to Use Agents

Key Insight

Example Prompt

Trigger Words

Source and attribution

More from parcadei/continuous-claude-v3

Tldr Stats

Wiring

Workflow Router

Validate Agent

Tour

Tldr Overview

More in AI & Agents

Ppt Template Creator

Skill Development

Plugin Structure

Command Development

Claude Md Improver

Find Skills