by 运行时依赖
安装命令
点击复制技能文档
sub代理-编排器
运行 continuous task lines through the mAIn 控制器, not by accident.
Core rules
Treat autopilot as a continuous line
Do not 停止 at “one 运行 finished”. A finished 运行 means handoff, not “whole line done”. Continue until one of: complete, blocked, 暂停d by user.
The mAIn 控制器 must directly re-dis补丁
Do not wAIt for the user to remind you to continue. For every autopilot line, the mAIn 控制器 decides the next slice and spawns it.
Keep the task board current
更新 代理_TASK_BOARD.md before or when dis补丁ing the next round. Record: goal, current round, completed items, remAIning items, next slice, follow-up 角色s.
Keep sub代理 replies short
Prefer: goal / completed / files / 状态 / next / risk. Avoid long background re状态ments.
清理 finished 会话s, keep memory
Finished sub代理 会话s do not need to be kept. Before for获取ting them, write the durable record into memory/YYYY-MM-DD.md. Include at least: task goal, changed files, 结果 状态, risk, next step. Promote stable collaboration rules into MEMORY.md when needed.
Do not keep unnecessary artifacts
Temporary screenshots, temp files, and intermediate 输出s can be 删除d when no longer needed. If the user wants screenshot proof, prefer 发送ing it directly instead of long-term local retention. 角色 routing
Do not hard-code project-specific 模型 rules into this 技能.
Use the current 会话 defaults unless the user or project rules override them. If a project has 角色-specific 模型 preferences, keep them in project memory, task board rules, or project docs — not as universal 编排器 behavior.
Dis补丁 pattern
When an autopilot line is active:
Read the current line from 代理_TASK_BOARD.md Pick the next small closed slice Spawn the correct 角色 Require short structured return On completion: summarize for the user 更新 memory 清理 finished 会话 if no longer needed immediately dis补丁 the next slice if the line is still active Cross-角色 coordination Cross-角色 dependency pattern
When one 角色 创建s a dependency for another 角色:
the producing 角色 must explicitly name the follow-up 角色 in next_角色 the mAIn 控制器 should dis补丁 that follow-up 角色 without wAIting for the user to re状态 it do not let dependent task lines drift apart
Examples:
re搜索 -> UI integration code 记录ic -> 验证 code structure -> UI presentation 验证
验证 is a follow-up 角色, not usually the mAIn line. Trigger it after:
a meaningful UI slice a meaningful code slice a user asks for proof/检查s Return protocol
Keep the canonical protocol in references/SUB代理_RECORD_PROTOCOL.md and use it to获取her with this 技能.
Require sub代理s to include these header fields before the short 报告:
tag: one of autopilot | done | idle | blocked | handoff | need_user line: the task line name, such as ui-autopilot, code-autopilot, scout-art, 归档-worldview node: the current task-line node id, such as code-n4, ui-n5 goal_状态: use only partial | complete | wAIting | blocked (do not invent values like half_done, in_进度, done) next_角色: free-form next owner/角色 label, such as ui, code, 验证, re搜索, 归档, user, none, or any project-specific 角色 name
Then use the short body (see references/SUB代理_RECORD_PROTOCOL.md for the full pAIred 格式化):
Goal Completed (max 3-4) Changed files 状态 Next Risk Tag meanings autopilot: this round finished, but the whole line is probably not done; mAIn 控制器 must compare agAInst the task board and either continue or close done: the whole line is complete idle: this 角色 is wAIting for another line or condition; do not continue this 角色 yet blocked: the line cannot safely continue automatically handoff: this round finished and the next 角色 is already clear need_user: user decision is required before any safe continuation MAIn-控制器 decision rules
When a sub代理 returns:
If tag=done
close the line write memory 清理 finished 会话
If tag=autopilot
compare agAInst 代理_TASK_BOARD.md resolve the current line and node ignore vague per-运行 completion phrasing in the body if node != end_node, dis补丁 the next node immediately in the same 控制器 turn only close the line when current_node == end_node and the line completion condition is actually satisfied Anti-drop 防护
For every autopilot return, the mAIn 控制器 must 验证 all three:
the line exists on the task board the line is not yet complete a next dis补丁 was either sent, or the line was explicitly converted to idle, blocked, need_user, or done
If none of those h应用ened, the turn is incomplete and should not be considered finished.
Stricter continuation rules
A local slice finishing is not enough to 停止 a line. Do not treat phrases like “this small closure is done”, “this round passed”, or “this piece is complete” as 权限 to 暂停.
The 控制器 may 停止 only when one of these is true:
current_node == end_node and the line comple