‹ 首页

orchestrator-loop

@mahsumaktas · 收录于 1 周前 · 上游提交 4 个月前

Orchestration pipeline for development tasks. The orchestrator delegates everything and never writes code directly.

场景任务编排开发流程

适合你，如果需要自动协调多个开发子任务

/ 下载安装
https://github.com/mahsumaktas/agent-evolution-kit/tree/main/skills/orchestrator-loop ↗
/ 通过 npx 安装 校验哈希
npx oh-my-skill add mahsumaktas/agent-evolution-kit/orchestrator-loop
/ 通过 bash 安装
curl -fsSL https://oh-my-skill.com/install.sh | bash -s -- mahsumaktas/agent-evolution-kit/orchestrator-loop
/ 已经装过?验证本机副本,不用重装
npx oh-my-skill verify mahsumaktas/agent-evolution-kit/orchestrator-loop
安装目标可用 --agent / --scope 或 --to 明确指定;省略时只会在唯一已存在的 agent 目录上自动选择,零命中或多命中会停止并提示。content_hash 缺失或不一致均拒装。
1GitHub stars
~622上下文体积 · 单文件
索引托管

怎么用

商店整理自技能原文 · 版本 c599c87 · 表述以原文为准
它做什么

安装后，Claude 会变成一个项目协调员，负责把开发任务拆解成调研、计划、执行、检查、报告五个步骤，并调用其他子技能或工具来完成每一步，自己绝不直接写代码。

什么时候触发

当你提出一个开发任务（如修改代码、添加功能）时触发。如果任务简单（单文件、改动少于20行、低风险、指令明确），会走快捷流程；否则走完整五步流程。

装好后可以这样说
触发完整五步流程。
触发快捷流程。
技能原文 SKILL.md作者撰写 · MIT · c599c87

Orchestrator Loop

The orchestrator DOES NOT WRITE CODE. This pipeline defines how the orchestrator delegates tasks.
Pipeline
RESEARCH --> PLAN --> IMPLEMENT --> REVIEW --> REPORT
    |          |        |            |          |
 delegate   orchestr.  delegate    delegate   orchestr.
(bridge.sh) (approve)  (spawn)    (spawn)   (report)
Step 1 -- RESEARCH (Gather Context)
  • If context is already clear --> SKIP (e.g., user provided file paths and explicit instructions)
  • If context is missing --> delegate via bridge.sh --research "..." or a research subagent
  • Output: Summary of current state + relevant files + risks
Step 2 -- PLAN (Design + Approval)
  • Large work (multi-file, architectural decisions): invoke the structured-brainstorming skill --> get user approval
  • Small work (single file, clear instructions): orchestrator writes a short summary --> get user approval
  • HARD-GATE: No implementation without approval. Do not proceed to Step 3 until the user says "go".
Step 3 -- IMPLEMENT (Delegate)
  • Invoke the subagent-execution skill --> spawn subagents for each task
  • The orchestrator only WATCHES: answers subagent questions, redirects if stuck
  • The orchestrator DOES NOT WRITE: creating/editing files directly is forbidden
  • Alternative for simple tasks: delegate via bridge.sh --code "..." to a coding subagent
Step 4 -- REVIEW (Verify)
  • Invoke the verification-gate skill
  • Check: spec compliance + code quality + tests
  • If it does not pass after 3 iterations --> escalate to the user; do NOT try to fix it yourself
Step 5 -- REPORT (Present to User)

The orchestrator reports:

  1. What was done (changed files + summary)
  2. What was skipped and why
  3. What requires human review
  4. Known limitations, if any
Shortcut Flow

Use the shortcut flow when ALL of the following are true:

  • [x] Single file change
  • [x] Less than 20 lines changed
  • [x] Low risk (does not touch a working system)
  • [x] Clear instructions (what to do is unambiguous)

Shortcut pipeline:

  1. Orchestrator writes a short summary --> gets user approval
  2. Delegates to a single coding subagent via bridge.sh --code "..."
  3. Verifies the result (read file + run)
  4. Reports
Red Flags

| If the orchestrator is thinking... | Reality | |---|---| | "This is simple, I will do it myself" | NO. Simplicity does not change the rules. Delegate. | | "Just one line" | Size does not matter. Writing directly is forbidden. | | "Spawning a subagent is slow" | Doing it right > doing it fast. | | "The pipeline is overkill" | Use the shortcut flow, but do NOT skip the pipeline. | | "I already know the answer" | Knowing is not writing. Delegate. |

按 MIT 许可原样转载,未经改动 · 在 GitHub 查看 →

评论

登录即可评论;带「已验证安装」的,是发布者名下有本店的安装或持有记录。
…