![Hyperplan Insight Bundle: [task title]](http://pic.xiahunao.cn/yaotu/Hyperplan Insight Bundle: [task title])
Hyperplan Insight Bundle: [task title]【免费下载链接】oh-my-openagentOmO: Just type mass ulw keyword with your prompt. Now you are the master of graph engineering.项目地址: https://gitcode.com/gh_mirrors/oh/oh-my-openagentOriginal User Request[restate the users planning request verbatim]Hard Constraints (Survived Adversarial Review)[constraint] — [which member surfaced it, why it survived attack]Decisions (Converged Through Debate)[decision] — [reasoning trail: who proposed, who attacked, how it was defended/refined]Risks Mitigations[risk] — [mitigation tied to a specific members finding]Open Questions (Unresolved Debate)[question] — [the contention] — [why the debate could not resolve it]Adversarial Provenanceskeptic findings that survived: [count]validator findings that survived: [count]researcher findings that survived: [count]architect findings that survived: [count]creative findings that survived: [count]Total findings filtered out (conceded/destroyed): [count]4. 简短告知用户Adversarial distillation complete. Handing the surviving insights to the plan agent for executable plan formalization. **不要**把这个 bundle 当作最终计划展示——它是 Phase 6 的原始输入不是交付物。 ### Phase 6强制 plan agent 交接 必须把洞察 bundle 派发给 plan agent。Lead 在 HYPERPLAN 中**不写可执行计划**——该职责按契约委托给专职规划者。这一分离不可协商。 1. **以同步前台任务派发交接**等待计划返回 typescript task({ subagent_type: plan, load_skills: [], run_in_background: false, description: Formalize hyperplan-distilled insights into executable plan, prompt: hyperplan-handoff The following insight bundle survived an adversarial 5-member cross-critique debate (skeptic/validator/researcher/architect/creative). Every claim here was either uncontested OR defended/refined under attack — conceded findings were already filtered out. Your task: produce an EXECUTABLE work plan from these insights. You do NOT need to re-explore the codebase or re-derive the constraints — they are already battle-tested. Your value is plan structure, sequencing, dependency analysis, parallelization opportunities, and explicit verification criteria per task. Hard rules for your plan: - Every Hard Constraint MUST be respected by the plan. - Every Risk MUST have its Mitigation woven into the relevant task. - Every Open Question MUST surface as a user-input gate BEFORE the dependent tasks can start. - Every task MUST have explicit success criteria. [paste the full Insight Bundle from Phase 5 here] /hyperplan-handoff })不要自己发明或预写计划。若在派发前发现自己开始起草任务停下来先派发。plan agent 的输出才是交付物。逐字呈现 plan agent 的输出给用户前缀一行出处说明*Plan derived from hyperplan adversarial review (5 members, 3 rounds) and formalized by the plan agent.* [plan agent output]若 plan agent 返回的是澄清问题而非计划原样转发给用户——规划者可以在承诺前先面谈。除非用户要求不要把计划保存到磁盘。HYPERPLAN 是规划咨询不是产出文件的流程——计划活在对话输出里。注意交接通道的边界plan agent不是团队成员不能走team_send_message必须用task(subagent_typeplan, ...)。并且 plan agent无法访问团队邮箱它需要的一切都必须包含在你派发的 bundle 里若规划者需要额外上下文由你Lead取回后以task_id续传resume重新派发不要新开一个 plan agent。Phase 7清理plan agent 的输出呈现给用户之后对 5 名成员逐一调用team_shutdown_request。Lead 可对每个成员team_approve_shutdownLead 有批准权。5 名成员全部关闭后调用team_delete({ teamRunId })清理运行时状态。用一行确认清理完成Hyperplan team disbanded.任何步骤失败都要把错误抛给用户并建议通过team_listteam_delete手动清理。反模式表绝不能做的事反模式为什么失败为节省时间跳过轮次对抗过滤器就是全部价值。跳过轮次 普通规划。软化成员提示词请客气点对抗压力就是机制。礼貌会毁掉这个技能。在第 3 轮完成前合成发现过早合成会保留弱发现。把被 concedeed 的发现放进洞察 bundleConceded 已败。bundle 只能含幸存者。Lead 在 Phase 5 写计划而不是在 Phase 6 交接交接就是契约。HYPERPLAN 对抗式蒸馏 专职规划者形式化。Lead 自写计划跳过了规划者的增值排序、依赖、成功标准把它变回普通编排。跳过planagent 派发bundle 已经是计划了bundle 是输入不是输出。plan agent 负责排序、并行化与验证关卡。没有派发HYPERPLAN 损失一半价值。在派发给 plan agent 前预写任务会把 plan agent 锚定在你的草稿上损害其独立判断。派发原始洞察让规划者去结构化。忘记清理团队泄漏运行时状态。永远执行 Phase 7。用delegate_task代替team_send_message这是不同的系统。team_*只用于成员间流量。用team_send_message把 bundle 发给 plan agent通道错了。plan agent 不是团队成员。交接必须用task(subagent_typeplan, ...)。从规划者 agentprometheus运行规划者不能编排团队。必须从 sisyphus 运行。在非主会话运行团队模式仅主会话可用。给 Lead 的实战笔记每个team_send_message对你而言都是fire-and-forget成员异步回复。发出第 N 轮消息后结束回合系统在下一回合注入成员回复。需要查看谁已回复、谁仍在工作时用team_status({ teamRunId })。成员彼此看不到对方的文本回复——只看到你经team_send_message转发的。你是信息经纪人Phase 3 与 4 中转的 bundle 就是它们的全部上下文。保持 bundle 精简——每条消息 ≤32KB。聚合发现超限就先总结再转发保留每条发现的实质。这与 team-mode 的message_payload_max_bytes默认 32768 字节的硬限制一致。技能明确禁止软化对抗提示词——敌意本身就是机制。Phase 6 的 plan-agent 交接同步运行run_in_background: false——在规划者返回前不要进入 Phase 7 清理。不要在 plan agent 返回前解散团队以防规划者需要你向某个成员转发澄清问题罕见但可能。plan agent没有团队邮箱访问权。它需要的一切都在你派发的 bundle 里。仓库源码佐证HYPERPLAN 底层的 team-mode启用与配置HYPERPLAN 依赖的 team-mode 默认关闭需在配置的team_mode块中启用并重启 opencode。官方文档 docs/guide/team-mode.md 给出的最小配置{ team_mode: { enabled: true, max_parallel_members: 4, max_members: 8, tmux_visualization: false } }完整 schema 共 11 个字段team_mode下enabledboolean默认false——总开关tmux_visualizationboolean默认false——可选的 tmux 窗格布局max_parallel_membersint1..8默认4——并行成员上限max_membersint1..8默认8——成员硬上限max_messages_per_runint1默认10000——单次运行消息上限max_wall_clock_minutesint1默认120——墙钟时间上限max_member_turnsint1默认500——成员回合上限base_dir可选字符串默认解析为~/.omo——团队存储根目录覆盖message_payload_max_bytesint1024默认32768——单条消息体上限即上文的 32KB bundle 限制recipient_unread_max_bytesint1024默认262144——单接收方收件箱上限mailbox_poll_interval_msint500默认3000——接收方轮询节奏Schema 本体定义在 team-core 中由 team-mode.ts 再导出AGENTS.md 完整记录了配置默认值。12 个team_*工具HYPERPLAN 用到的team_create、team_send_message、team_shutdown_request、team_approve_shutdown、team_delete、team_status只是其中一部分。全套 12 个工具在 tool-registry-team-tools.ts 中注册且仅在team_mode.enabled时注册未启用时该函数直接返回空对象工具源码用途team_createtools/lifecycle.ts按命名或内联 TeamSpec 拉起团队与成员会话team_deletetools/lifecycle.ts拆除状态、邮箱、任务列表、worktree、可选 tmuxteam_shutdown_requesttools/lifecycle.ts成员或 Lead 请求自身关闭team_approve_shutdowntools/lifecycle.tsLead 批准关闭team_reject_shutdowntools/lifecycle.tsLead 拒绝关闭并附理由team_send_messagetools/messaging.ts发送给成员名或*广播team_task_createtools/tasks.ts在共享列表上创建任务team_task_listtools/tasks.ts列出任务按状态/属主过滤team_task_updatetools/tasks.ts认领/完成/删除原子文件锁team_task_gettools/tasks.ts获取单个任务team_statustools/query.ts团队运行全景成员、任务、邮箱team_listtools/query.ts列出已声明 活跃团队消息机制异步邮箱而非同步 RPCHYPERPLAN 的三轮辩论能成立依赖 team-mode 的异步邮箱设计team_send_message是 fire-and-forget接收方通过轮询mailbox_poll_interval_ms默认 3000ms收信并单独 ack。实现细节在 team-mailbox/send/poll/ack/inbox与 team-state-store/带原子锁的持久化运行时状态中底层 harness 无关的原语抽取在 packages/team-core。存储布局~/.omo用户级或project/.omo项目级~/.omo/ ├── teams/{name}/config.json # 声明的团队规格 └── runtime/{teamRunId}/ ├── state.json # 持久化运行时状态 ├── inboxes/{member}/{uuid}.json # 邮箱原子单消息文件 ├── inboxes/{member}/.delivering-{uuid}.json # 瞬态实时投递预留 ├── inboxes/{member}/processed/ # 已 ack 消息 ├── tasks/{id}.json # 共享任务列表 ├── tasks/claims/ # 任务认领记录 └── tasks/.highwatermark # 任务列表 id 分配器【免费下载链接】oh-my-openagentOmO: Just type mass ulw keyword with your prompt. Now you are the master of graph engineering.项目地址: https://gitcode.com/gh_mirrors/oh/oh-my-openagent创作声明：本文部分内容由AI辅助生成（AIGC），仅供参考 Hyperplan Insight Bundle: [task title]
Hyperplan Insight Bundle: [task title]【免费下载链接】oh-my-openagentOmO: Just type mass ulw keyword with your prompt. Now you are the master of graph engineering.项目地址: https://gitcode.com/gh_mirrors/oh/oh-my-openagentOriginal User Request[restate the users planning request verbatim]Hard Constraints (Survived Adversarial Review)[constraint] — [which member surfaced it, why it survived attack]Decisions (Converged Through Debate)[decision] — [reasoning trail: who proposed, who attacked, how it was defended/refined]Risks Mitigations[risk] — [mitigation tied to a specific members finding]Open Questions (Unresolved Debate)[question] — [the contention] — [why the debate could not resolve it]Adversarial Provenanceskeptic findings that survived: [count]validator findings that survived: [count]researcher findings that survived: [count]architect findings that survived: [count]creative findings that survived: [count]Total findings filtered out (conceded/destroyed): [count]4. 简短告知用户Adversarial distillation complete. Handing the surviving insights to the plan agent for executable plan formalization. **不要**把这个 bundle 当作最终计划展示——它是 Phase 6 的原始输入不是交付物。 ### Phase 6强制 plan agent 交接 必须把洞察 bundle 派发给 plan agent。Lead 在 HYPERPLAN 中**不写可执行计划**——该职责按契约委托给专职规划者。这一分离不可协商。 1. **以同步前台任务派发交接**等待计划返回 typescript task({ subagent_type: plan, load_skills: [], run_in_background: false, description: Formalize hyperplan-distilled insights into executable plan, prompt: hyperplan-handoff The following insight bundle survived an adversarial 5-member cross-critique debate (skeptic/validator/researcher/architect/creative). Every claim here was either uncontested OR defended/refined under attack — conceded findings were already filtered out. Your task: produce an EXECUTABLE work plan from these insights. You do NOT need to re-explore the codebase or re-derive the constraints — they are already battle-tested. Your value is plan structure, sequencing, dependency analysis, parallelization opportunities, and explicit verification criteria per task. Hard rules for your plan: - Every Hard Constraint MUST be respected by the plan. - Every Risk MUST have its Mitigation woven into the relevant task. - Every Open Question MUST surface as a user-input gate BEFORE the dependent tasks can start. - Every task MUST have explicit success criteria. [paste the full Insight Bundle from Phase 5 here] /hyperplan-handoff })不要自己发明或预写计划。若在派发前发现自己开始起草任务停下来先派发。plan agent 的输出才是交付物。逐字呈现 plan agent 的输出给用户前缀一行出处说明*Plan derived from hyperplan adversarial review (5 members, 3 rounds) and formalized by the plan agent.* [plan agent output]若 plan agent 返回的是澄清问题而非计划原样转发给用户——规划者可以在承诺前先面谈。除非用户要求不要把计划保存到磁盘。HYPERPLAN 是规划咨询不是产出文件的流程——计划活在对话输出里。注意交接通道的边界plan agent不是团队成员不能走team_send_message必须用task(subagent_typeplan, ...)。并且 plan agent无法访问团队邮箱它需要的一切都必须包含在你派发的 bundle 里若规划者需要额外上下文由你Lead取回后以task_id续传resume重新派发不要新开一个 plan agent。Phase 7清理plan agent 的输出呈现给用户之后对 5 名成员逐一调用team_shutdown_request。Lead 可对每个成员team_approve_shutdownLead 有批准权。5 名成员全部关闭后调用team_delete({ teamRunId })清理运行时状态。用一行确认清理完成Hyperplan team disbanded.任何步骤失败都要把错误抛给用户并建议通过team_listteam_delete手动清理。反模式表绝不能做的事反模式为什么失败为节省时间跳过轮次对抗过滤器就是全部价值。跳过轮次 普通规划。软化成员提示词请客气点对抗压力就是机制。礼貌会毁掉这个技能。在第 3 轮完成前合成发现过早合成会保留弱发现。把被 concedeed 的发现放进洞察 bundleConceded 已败。bundle 只能含幸存者。Lead 在 Phase 5 写计划而不是在 Phase 6 交接交接就是契约。HYPERPLAN 对抗式蒸馏 专职规划者形式化。Lead 自写计划跳过了规划者的增值排序、依赖、成功标准把它变回普通编排。跳过planagent 派发bundle 已经是计划了bundle 是输入不是输出。plan agent 负责排序、并行化与验证关卡。没有派发HYPERPLAN 损失一半价值。在派发给 plan agent 前预写任务会把 plan agent 锚定在你的草稿上损害其独立判断。派发原始洞察让规划者去结构化。忘记清理团队泄漏运行时状态。永远执行 Phase 7。用delegate_task代替team_send_message这是不同的系统。team_*只用于成员间流量。用team_send_message把 bundle 发给 plan agent通道错了。plan agent 不是团队成员。交接必须用task(subagent_typeplan, ...)。从规划者 agentprometheus运行规划者不能编排团队。必须从 sisyphus 运行。在非主会话运行团队模式仅主会话可用。给 Lead 的实战笔记每个team_send_message对你而言都是fire-and-forget成员异步回复。发出第 N 轮消息后结束回合系统在下一回合注入成员回复。需要查看谁已回复、谁仍在工作时用team_status({ teamRunId })。成员彼此看不到对方的文本回复——只看到你经team_send_message转发的。你是信息经纪人Phase 3 与 4 中转的 bundle 就是它们的全部上下文。保持 bundle 精简——每条消息 ≤32KB。聚合发现超限就先总结再转发保留每条发现的实质。这与 team-mode 的message_payload_max_bytes默认 32768 字节的硬限制一致。技能明确禁止软化对抗提示词——敌意本身就是机制。Phase 6 的 plan-agent 交接同步运行run_in_background: false——在规划者返回前不要进入 Phase 7 清理。不要在 plan agent 返回前解散团队以防规划者需要你向某个成员转发澄清问题罕见但可能。plan agent没有团队邮箱访问权。它需要的一切都在你派发的 bundle 里。仓库源码佐证HYPERPLAN 底层的 team-mode启用与配置HYPERPLAN 依赖的 team-mode 默认关闭需在配置的team_mode块中启用并重启 opencode。官方文档 docs/guide/team-mode.md 给出的最小配置{ team_mode: { enabled: true, max_parallel_members: 4, max_members: 8, tmux_visualization: false } }完整 schema 共 11 个字段team_mode下enabledboolean默认false——总开关tmux_visualizationboolean默认false——可选的 tmux 窗格布局max_parallel_membersint1..8默认4——并行成员上限max_membersint1..8默认8——成员硬上限max_messages_per_runint1默认10000——单次运行消息上限max_wall_clock_minutesint1默认120——墙钟时间上限max_member_turnsint1默认500——成员回合上限base_dir可选字符串默认解析为~/.omo——团队存储根目录覆盖message_payload_max_bytesint1024默认32768——单条消息体上限即上文的 32KB bundle 限制recipient_unread_max_bytesint1024默认262144——单接收方收件箱上限mailbox_poll_interval_msint500默认3000——接收方轮询节奏Schema 本体定义在 team-core 中由 team-mode.ts 再导出AGENTS.md 完整记录了配置默认值。12 个team_*工具HYPERPLAN 用到的team_create、team_send_message、team_shutdown_request、team_approve_shutdown、team_delete、team_status只是其中一部分。全套 12 个工具在 tool-registry-team-tools.ts 中注册且仅在team_mode.enabled时注册未启用时该函数直接返回空对象工具源码用途team_createtools/lifecycle.ts按命名或内联 TeamSpec 拉起团队与成员会话team_deletetools/lifecycle.ts拆除状态、邮箱、任务列表、worktree、可选 tmuxteam_shutdown_requesttools/lifecycle.ts成员或 Lead 请求自身关闭team_approve_shutdowntools/lifecycle.tsLead 批准关闭team_reject_shutdowntools/lifecycle.tsLead 拒绝关闭并附理由team_send_messagetools/messaging.ts发送给成员名或*广播team_task_createtools/tasks.ts在共享列表上创建任务team_task_listtools/tasks.ts列出任务按状态/属主过滤team_task_updatetools/tasks.ts认领/完成/删除原子文件锁team_task_gettools/tasks.ts获取单个任务team_statustools/query.ts团队运行全景成员、任务、邮箱team_listtools/query.ts列出已声明 活跃团队消息机制异步邮箱而非同步 RPCHYPERPLAN 的三轮辩论能成立依赖 team-mode 的异步邮箱设计team_send_message是 fire-and-forget接收方通过轮询mailbox_poll_interval_ms默认 3000ms收信并单独 ack。实现细节在 team-mailbox/send/poll/ack/inbox与 team-state-store/带原子锁的持久化运行时状态中底层 harness 无关的原语抽取在 packages/team-core。存储布局~/.omo用户级或project/.omo项目级~/.omo/ ├── teams/{name}/config.json # 声明的团队规格 └── runtime/{teamRunId}/ ├── state.json # 持久化运行时状态 ├── inboxes/{member}/{uuid}.json # 邮箱原子单消息文件 ├── inboxes/{member}/.delivering-{uuid}.json # 瞬态实时投递预留 ├── inboxes/{member}/processed/ # 已 ack 消息 ├── tasks/{id}.json # 共享任务列表 ├── tasks/claims/ # 任务认领记录 └── tasks/.highwatermark # 任务列表 id 分配器【免费下载链接】oh-my-openagentOmO: Just type mass ulw keyword with your prompt. Now you are the master of graph engineering.项目地址: https://gitcode.com/gh_mirrors/oh/oh-my-openagent创作声明：本文部分内容由AI辅助生成（AIGC），仅供参考