Agent Orchestration

作者 parcadeid07ff4b06b62无许可证3.9K 个星标收录于 2026年10月8日更新于 2026年10月8日仓库8个月前更新

Agent Orchestration Rules

仅含说明AI & Agents
AI 生成的概览

指导智能体将实现工作委派给子智能体,以节省主上下文令牌。

功能
该技能提供规则,用于判断何时应启动实现子智能体,而不是在主对话中直接完成工作。它对比了消耗上下文的直接做法与将多文件实现、计划阶段以及带测试的功能开发委派给智能体的做法,并给出示例委派提示词和触发词。它产出的是指导,而不是文件或代码。
适用场景
当用户要求实现、构建或创建功能,或要求执行某个计划阶段,并且你希望保持主上下文精简时使用。它也适用于判断某项任务是否小到不值得使用智能体。
运行要求
无需工具、软件包或凭据;仅为说明性指令,不附带脚本。

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)

Right - preserves context:

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

When to Use Agents

Task TypeUse Agent?Reason
Multi-file implementationYesAgent handles complexity internally
Following a plan phaseYesAgent reads plan, implements
New feature with testsYesAgent can run tests
Single-line fixNoFaster to do directly
Quick config changeNoOverhead 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.

Trigger Words

When user says these, consider using an agent:

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

来源与署名

来源:parcadei/continuous-claude-v3位于.claude/skills/agent-orchestration提交d07ff4b

许可证: 无许可证

内容归原作者所有。SourceWeft 从公开仓库中收录这些内容。

举报或申请下架